Manage leads

Seekers can also book appointments themselves — from the slots you publish on Kontinue’s Availability tab (weekly windows, blocked dates, notice and advance-booking rules; see Kontinue CRM → Appointment availability). Keep it current so self-booked discovery days land when you’re actually free.

If Kariant administration reassigns or archives a lead, open appointments are cancelled, open quotes expire and open document requests are waived. Restoring the lead does not silently reopen any of them.

An appointment-account safety update is prepared for rollout. Your signed-in identity must match the assigned partner account, and the inquiry and appointment must agree on both parties. Missing or inconsistent older account records stop the operation for Kariant review; another user with the same identifier in a different account context is not the same participant.

Retries of successful requests recheck current access and return the recorded result without repeating the appointment change, even if its original time has passed. New bookings and reschedules still obey current time and availability rules. Contact support for an account-reconciliation error rather than trying to bypass it with a new request.

The prepared quote-safety update binds quote reads and actions to the recorded partner account and both inquiry parties. Only the assigned active partner can send; the user decides whether to express non-binding interest. Replaying a sent quote rechecks current assignment, standing and the stored quote, so an old receipt cannot restore access after reassignment. Missing older account evidence needs support reconciliation, not another quote or payment. Background email and expiry rollout remains a separate validation step.

New quote notices in the prepared background update link to your partner account without embedding private financial details, territories or decisions. Delayed new-quote notices are withheld if the listing or partner is no longer active. An old email cannot restore access or authorize payment. Expiry can close an outdated quote without notifying guessed accounts; unresolved records need Kariant review. Final mail delivery, notification-access and expiry-job validation remain open before rollout.

The prepared sender update checks current account access and verified email again before sending. It retries temporary failures only before a delivery attempt starts; uncertain deliveries and older conflicting records require review instead of automatic resends. Deletion of either linked account suppresses pending quote mail and removes its private context. Check the current partner Quotes view or contact support rather than issuing another quote or charging again to recover a notice.

The prepared notification-access update checks your exact signed-in account context and clears private notices when it changes. Mark-read is confirmed before navigation; failed or repeated clicks cannot open a stale notice. The badge describes the latest 100 notifications. Xtended partner activity and recent notifications use /partner/kontinue and /partner/notifications, separate from main Kariant partner pages.

The prepared appointment-notification update sends a generic in-app notice only when the current appointment, assigned parties and account contexts agree. Ordinary decisions notify the other party; recorded Kariant Admin decisions can notify both. Meeting details stay in the authorized Appointments view. Retries preserve read state, and conflicting historical notices remain for review. Production rollout, appointment email and some other event producers remain separate work.

The prepared listing-review update creates a generic Private listing update notice only when your current listing ownership, verified account context and the recorded Kariant review agree. It links to /partner/listings on Xtended without copying private review reasons into the preview. Listing-review email is held in this source update until recipient checks and final delivery are migrated; existing queued mail is not recalled. Check your current Listings view directly, and contact support if an older notice needs reconciliation. This does not confirm a production rollout.

The prepared lead-stage update rechecks your current verified partner account, recorded assignment, listing and account standing before any stage change or successful retry. An Admin claim alone does not grant partner stage access. Missing account scope requires Kariant reconciliation rather than a guessed identity. Verified guest inquiries can still be managed, but receive no account inbox notice. This stage-change command does not request paid AI or debit Koins/Sikka; other automation paths are separate controls. The user notice is generic; stage email stays held in this source update pending protected delivery checks. This is local preparation, not confirmation of a production rollout.

A separate prepared administration update rechecks current Kariant administrator access before reassignment, archival, restoration or a saved-result retry. Valid changes keep the inquiry and linked records in one transaction; inconsistent version history requires review. Restoring the inquiry does not revive cancelled appointments, expired quotes or waived requests. Check the current authorized pipeline and contact support with the inquiry reference. This is an administrator-access safeguard, not completion of target-account reconciliation, membership synchronization or email delivery, and it is not yet a production rollout.

The next prepared administration update validates current receiving-partner approval, listing ownership, verified account context and both parties before assigning or restoring access. A plan label by itself is insufficient. A mismatched linked conversation, appointment or quote stops the complete operation for review. Independently closed conversations do not reopen with a lead, and cancelled appointments, expired quotes and waived requests remain closed. Archival can still remove access from a suspended account. Historical reconciliation, membership synchronization and delivery remain separate work; no live rollout is implied.

The prepared network-membership update temporarily holds roster, announcement and support-ticket functions before private access while their complete tenant-aware contracts are migrated. Existing records are retained, not deleted. New stage and Admin events build separate per-inquiry evidence; an older event cannot revive or revoke a newer grant, and one inquiry cannot overwrite another. This does not change paid membership or charge Koins/Sikka. Admin lifecycle notices and email remain held pending protected delivery. Contact support rather than recreating historical tickets or paying again; this statement describes source preparation, not a live rollout.

Your Xtended /partner workspace belongs to the multi-category platform, separate from the main Kariant /partner workspace. Only the franchise category is currently enabled. The new network evidence is explicitly franchise-scoped; future dealership, distribution, licensing and other category workflows need their own approved capabilities and lifecycle contracts, not copied franchise permissions or another master identity.

Older notices without verified account scope are retained for Kariant review, not assigned from a matching identifier. Cross-channel forwarding and automatic push-token registration are paused in this prepared source update until the complete delivery path is account-context safe; no production rollout is implied. Your current partner pipeline remains the place to check activity directly. Historical repair and some event producers still require migration.

The prepared private-read update uses your recorded partner account context for incoming inquiries and partner appointments. Your own user-side inquiries and meetings are a separate view, not combined with the partner pipeline. Unavailable or denied reads clear old live results and show recovery guidance. If an older record is missing, contact support; do not recreate it merely to work around account-scope reconciliation.