Kontinue — your seeker pipeline

Submitting an inquiry on a brand detail page creates a lead shared between you and that franchisor. As the franchisor moves your application through stages you get real-time notifications, and every change is recorded on the lead’s timeline.

Appointments (like discovery-day bookings) are scheduled against the same lead, and Messages holds your direct conversations — both reachable from /kontinue and /messages.

Text conversations remain available in both directions. New file attachments are temporarily paused until Kariant’s membership-aware malware scanning, quarantine and short-lived delivery broker is available; the interface labels this state instead of accepting a file that cannot be processed safely.

Threads are live in both directions: a typing indicator shows when the franchisor is writing, and your messages show a read indicator once they have been read on the other side.

The Discovery Day page (/discovery-day) lists live events published by franchisors — date and time, format, and available spots. RSVP requires a signed-in, email-verified account. Confirm or cancel sends one protected request to Kariant; the page waits for the server result instead of changing the seat count optimistically. The server checks that the event is active, upcoming, still has capacity and belongs to an active franchisor, then changes your RSVP and its seat count together. A stale, full or closed event shows an error you can recover from instead of a false confirmation. Your confirmed or cancelled RSVP appears in the franchisor’s command center and raises their bell. Events a franchisor invited you to carry a “You’re invited” badge (the invite also emails you and raises your bell). If a franchisor cancels an event you had confirmed, you are notified too.

When you book an appointment, the dates and time slots you can pick come from the franchisor’s published availability: the weekly windows they’ve opened, minus any dates they’ve blocked, respecting their minimum-notice and how-far-ahead rules. If that schedule is missing or cannot be verified, Kariant says so and assumes no hours; use Messages to coordinate instead.

The assigned franchisor can propose a one-off manual time from their own lead workspace without publishing recurring availability. Seekers still cannot self-book until a complete schedule is published.

Booking opens once your lead has a franchisor assigned. Until then the Book action is disabled with a note explaining why — so every appointment you schedule reaches a real franchisor on the other side.

An appointment-account safety update is prepared for rollout. Scheduling and changes must match the accounts recorded on the inquiry and appointment. If older records are missing or disagree, booking stops for Kariant review rather than guessing an account. Contact support if you see an account-reconciliation message; changing the account or repeatedly submitting a new request will not repair that record.

For a retry of an already successful request, the prepared update rechecks current access and returns the original result without another appointment change. The original appointment time passing does not by itself invalidate that receipt. A new booking or reschedule must still meet current notice and availability rules.

A private-quote safety update is also prepared for rollout. Quotes must match your recorded user account context and the current inquiry. Accepting a quote records non-binding interest, not a payment or franchise agreement. A successful retry returns the recorded decision only while current access is still valid. If Quotes is unavailable or an older record needs reconciliation, contact support with the inquiry reference; do not create another account or payment to recover access.

The prepared quote-notice update keeps investment amounts, territories, brand details and decisions out of new emails and bell notices. Sign in to your own account to review the current quote. An email is a notice, not proof that an offer is still available, accepted or payable. Final delivery and notification-access validation are still required before this update is rolled out.

The prepared sender update rechecks current access and your verified email before sending. A changed address, expired new quote or revoked access can stop a pending notice; it is not silently redirected to another mailbox. If delivery may already have happened, the system holds it for review rather than automatically sending another copy. Review the current Quotes view or contact support; do not create a duplicate quote or payment to recover an email.

The prepared notification-access update limits your inbox to the exact signed-in account context. Switching accounts clears private rows and pending actions; a failed mark-read does not open another page. The unread badge covers the latest 100 notifications, not your entire history. Older notices without verified account scope remain held for review rather than being shown to a guessed account.

The prepared appointment-notification update checks the current appointment, both account contexts and account availability before creating a generic notice. It does not copy meeting links, addresses or times into the preview. Open Appointments in Kontinue for current details. Old or conflicting notices are retained for review, not reassigned; this local update does not confirm production rollout or complete appointment email delivery.

A separate prepared listing-review update sends generic in-app notices only to the verified current partner account, not to seekers or a guessed owner. Listing-review email remains held in that source update until its complete delivery path is verified. A missing notification does not establish whether an opportunity is approved or available; review its current public page or your authorized inquiry. No production rollout is implied.

The prepared inquiry-stage update creates a generic Private inquiry update notice only when the current inquiry, assigned partner and both verified account contexts agree. Sign in and open the inquiry for its current stage; no brand or stage is copied into the notice preview. Stage emails, including the legacy guest path, are held in this source update until recipient admission and final delivery are verified. Existing queued emails are not recalled. Verified guest inquiries remain manageable by their assigned partner but do not acquire a fictional account inbox. No production rollout is implied.

A prepared administration safety update requires a current authorized Kariant administrator before an inquiry can be reassigned, archived or restored, including retries of a previously completed request. Invalid record versions stop the operation for review instead of silently resetting history. Restoring an inquiry does not automatically rebook cancelled appointments, reopen expired quotes or renew waived document requests. Contact support with the inquiry reference rather than submitting another application. This local update does not confirm production rollout or complete notification delivery.

The next prepared administration update also checks the actual receiving partner and both recorded account contexts before assigning or restoring access. An inconsistent linked conversation, appointment or quote stops the complete change for review. A conversation reopens only when its recorded closure belongs to that inquiry archive; independently closed threads stay closed. Verified guests do not gain an account inbox until their inquiry is securely linked. This update does not complete membership synchronization or notification delivery and is not a live rollout.

A further prepared safety update temporarily holds the franchise operations hub, announcements and support-ticket functions while their account-context records and readers are migrated together. Historical tickets and announcements are preserved. This is separate from submitting a marketplace inquiry and from paid Partner membership. If you receive the network migration message, contact support with your inquiry reference; do not create another account or payment. Older stage, archive or reassignment events cannot restore network access. Admin lead lifecycle alerts also remain held until current-recipient delivery is ready. These are source changes, not confirmation that they are deployed.

Kariant Xtended supports a multi-category product structure. Franchises are the initial live category; dealerships and distributorships, manufacturing, licensing, channel partnerships, operator rights, joint ventures and institutional partnerships remain gated. Franchise-specific network access does not grant access to those future categories.

Cross-channel forwarding and automatic push-token registration are paused in this prepared source update while account-context checks are completed through every delivery step. This is not confirmation that production push delivery has changed. Open the current inquiry or Quotes view directly if a notice is unavailable, and contact support for historical reconciliation instead of recreating the inquiry.

The prepared private-read update also separates user and partner appointment histories and verifies the recorded account context. The pipeline, appointment list, deal room and booking page reset when the signed-in identity changes. If a verified connection is lost, the live reader clears old results and offers recovery rather than displaying cached private records as current. Older records without confirmed account scope may need support reconciliation; an empty list is not proof that historical inquiries never existed.

Where enabled, inquiry receipts and lifecycle emails are notices about your inquiry, not a guarantee of immediate delivery. The prepared stage-email update remains held until recipient and final-delivery checks are complete, including for guest inquiries. Open your current inquiry in Kontinue or contact support if a message is missing; do not submit a duplicate inquiry just to recover an email.

Quote notices link to the private Quotes view; review the current record there rather than treating an email as an available offer. For appointments, check the current meeting record for confirmation, cancellation or rescheduling. A calendar attachment, where included, is a copy of the scheduled details and may no longer reflect a later change. Appointment email and reminder rollout require separate validation.

Supported in-app notices appear in the bell and at /notifications. Email and in-app delivery may differ; a missing notice does not establish that an inquiry or decision is absent.

Use your own signed-in account and the authorized inquiry view to review private details. If a record appears under the wrong account or an older timeline is unavailable, contact support with its reference; do not share private documents or create another account to bypass an access problem. Account-context and timeline controls remain part of the staged safety validation.