Kontinue CRM

Signed-in verified inquiries can become leads immediately. A guest submission is captured in a private verification queue first and is not exposed in your pipeline until the guest proves control of the submitted mailbox; after verification, the canonical lead carries the seeker’s submitted capital, country, source, and message plus its activity timeline.

You move leads through stages; the seeker sees status updates in real time on their side, and every transition is recorded on the timeline for both parties. Stage changes, quotes, and appointment updates also email the seeker automatically — your pipeline actions keep candidates informed without extra work.

Appointments (discovery days, calls) are scheduled against leads; quotes and documents attach to the same record. Booking confirmations and automatic reminders (about 24 hours and 1 hour before) are emailed to both sides — reminders re-arm when an appointment is rescheduled, and a past confirmed appointment that didn’t happen can be marked as a no-show so your pipeline history stays honest.

Message threads are live in both directions: read indicators show when the seeker has read your message, a typing indicator shows when they’re writing, and you can star conversations in your Messages inbox — the starred filter keeps priority threads one tap away.

After Kariant verifies that an inquiry genuinely belongs to one of your listings, a deterministic server-side rubric runs automatically at zero Koins. It uses the available budget, geography, contact, account, and declared-fit inputs to produce a 0–100 score with visible reasons; dimensions without evidence remain unassessed.

AI refinement is separate and currently unavailable from the lead workflow. It never starts because an inquiry arrived, was verified or assigned, or because your wallet has funds. If Kariant later offers it, an authorized franchisor must initiate a separate action and confirm the displayed Koin/Sikka price before it can run. The zero-Koin rules score remains available without AI.

You control when seekers can book: the Availability tab in Kontinue is where you publish your booking windows — one window per weekday (enable or disable each day and set its start and end time), plus blocked dates, a minimum-notice requirement, and how far ahead bookings are allowed.

Seekers can book discovery calls, FDD reviews and site visits only when you have published valid availability. A missing schedule does not authorize default office hours. Publish your real weekly windows, blocked dates and notice rules before offering self-booking; you may propose a manual appointment as the assigned partner.

A verified lead triggers an email alert to the listing owner’s account email with the lead’s core details and a deep link into Kontinue, plus in-console notifications. An unverified guest submission triggers no franchisor disclosure or paid processing.

Publish Discovery Day events from the Command Center at /franchisor/discovery-days: pick the brand, date and time, format (virtual, in-person, or hybrid), venue or meeting link, and available spots. Published events appear on the seeker Discovery Day page, and accepted seeker RSVPs stream back into your command center live.

You manage your own events — adjust spots inline or cancel an event any time (cancelled events disappear from the seeker list immediately, and confirmed attendees are notified of the cancellation automatically). The same page pre-screens invite candidates from your pipeline by fit score and drafts AI invitation emails.

Invitations are first-class: inviting a pipeline lead emails the candidate, raises their notification bell, and shows a “You’re invited” badge on their Discovery Day page. Invitations go to people already in your pipeline — the invitation email is addressed from the lead’s own record on your board, and it is only sent for events you own, so nobody can be mailed by way of a hand-typed address. Seat counts maintain themselves — Kariant verifies the signed-in seeker, your current account standing, event status and capacity, then commits the RSVP and seat change together. Cancellations give exactly one seat back, full events reject new confirmations, and stale retries cannot double-adjust capacity. Accepted confirmations and cancellations appear in your RSVP list and notify your verified account through the shared bell/email rail; the seeker cannot choose the notification recipient. If an invitation row can’t be matched back to a lead on your board, it shows an “unverified — no email was sent” badge instead of contact details.

Each event carries its own attendee dashboard with the live RSVP list and per-attendee status. After an event ends, one automated follow-up email goes out to attendees — a single touch, not a drip sequence.