Configure

Live chat

Every conversation on Quincer is simultaneously an AI chat and a live chat. Reps can jump in mid-conversation, type, pause the AI, and hand back. Visitors see no interruption.

The inbox

Open Conversations from the dashboard sidebar. You'll see three tabs:

• Active — visitors currently on your site with the widget open.
• Escalated — conversations where the AI has asked for a human.
• All — the full history, filterable by persona, tier, status, or source page.

Each row shows the visitor identity (name if captured, otherwise IP + location), BANT score, persona, the current page they're on, and a live preview of the last message.

Getting notified

There are four places an alert can land:

• Dashboard bell — red dot when a conversation escalates or a Hot lead starts.
• Browser notifications — opt in from the dashboard header.
• Slack — if connected, the AI posts alerts in the channel you chose. Reps can reply from Slack threads or click Take over to drive the live chat.
• Telegram — if connected, escalations post into your Telegram group with inline Take over / Hand back buttons.
• Email digest — one email per day, or instant for Hot leads.

Notification preferences live in Settings → Notifications.

Where the three surfaces fit

Live chat happens in three places. They complement each other; use the right surface for the job.

• Quincer portal (Dashboard → Live chat) — the full experience. Every active conversation, AI copilot suggestions, internal notes, transfer between teammates, resolve, close, and a force-release button when an integration bot holds the lock. Use this when you want to drive a conversation from the start.
• Slack and Telegram — escalation surfaces. They only light up when the AI explicitly hands off a conversation using slack_escalate_question / telegram_escalate_question (because a visitor asked for a human or the AI couldn't answer). Conversations you take over from the portal are not auto-mirrored there.

Taking over from the portal

1. Click a conversation in the inbox. You'll see the full transcript and a composer at the bottom.
2. Click Take over. The AI stops replying; the visitor sees a brief “I've sent your message to a teammate” note on their next send.
3. Type your reply and hit Enter. Messages appear under your name.
4. When done, click Hand back to AI (returns to AI-led) or Resolve (closes the conversation).

Internal notes

Click the Notes tab in the conversation detail to leave notes your team can see but the visitor cannot. Useful for recording context before handing a ticket to another rep.

Taking over from Slack

Prerequisite: the AI escalated the conversation via slack_escalate_question. That's the only time a message appears in your channel — conversations you drive from the portal don't post here.

The escalation message has three buttons and two reply modes:

• Quick answer — reply in the thread without tapping Take over. Your reply streams back to the visitor prefixed with “I checked with my team”, and the AI continues to drive the conversation.
• Live takeover — click Take over. The AI pauses. Every thread reply is forwarded to the visitor as you. Visitor follow-ups appear in the thread as 💬 {visitor}: {message} so you see what they're saying, not just the first question.

During a live takeover the buttons become:

• ✋ Hand back to AI — releases the lock. AI resumes. Conversation stays open.
• 🔒 Close — terminal. Conversation is marked closed, the lock released, the visitor sees “This conversation has ended. Send a message to start a new one.” Future visitor messages start a fresh session with the AI.
• Open in Quincer — deep-links to the conversation in the portal.

No setup needed on your end — Quincer's Slack app ships with Interactivity, /quincer, and event subscriptions pre-wired. Connect once at Integrations → Slack and the Take over flow is available in every workspace channel the app is invited to.

Taking over from Telegram

Prerequisite: the AI escalated the conversation via telegram_escalate_question. A message appears in your configured group only when that happens — portal-driven conversations don't post here.

The escalation message has a Take over button. Two reply modes mirror Slack:

• Quick answer — reply to the escalation message without tapping Take over. Your reply is relayed to the visitor prefixed with “I checked with my team”, and the AI continues.
• Live takeover — tap 🎧 Take over. Reply to the escalation message (or the “X is now live” confirmation posted below it — either anchor works) and every reply goes to the visitor as you. Visitor follow-ups appear threaded under the escalation as 💬 {visitor}: {message}.

During a live takeover the inline keyboard shows three actions:

• ✋ Hand back to AI — releases the lock. AI resumes.
• 🔒 Close — terminal. Conversation closed, session ended for the visitor.
• Open in Quincer — deep-links to the conversation in the portal.

Required BotFather setup: run /setprivacy and choose Disable so the bot can read group replies. See Telegram.

Closing a conversation

A closed conversation is terminal — the visitor's session ends, their next widget message starts fresh, and the thread drops from the live inbox. Close from any of the three surfaces:

• Portal — the Resolve button on the conversation header.
• Slack — tap 🔒 Close on the escalation message (only available after takeover).
• Telegram — tap 🔒 Close on the escalation message (only available after takeover).

When a conversation is closed from the portal, the Slack/Telegram thread gets a 🔒 closed by X note so the integration operator knows to move on. When closed from Slack/Telegram, the widget shows the visitor “This conversation has ended. Send a message to start a new one.” and their next message opens a fresh conversation with the AI.

Working hours

Under Settings → Availability you can set business hours and OOO windows. Outside hours, the AI gives a different closing message (“The team is offline — we'll reply first thing tomorrow”) and all conversations are held in the Escalated tab for morning review.

Closing a conversation

Click the Close button in the conversation detail. This marks it resolved, triggers the follow-up email (if enabled), and syncs the final state to your CRM. You can always reopen from the detail view.

Mobile

The full inbox works on mobile browsers. Dedicated iOS and Android apps are on the roadmap for Scale customers.