Configure
Sales automation
Quincer doesn't just answer questions. It qualifies every visitor against your BANT profile, books meetings with the right rep while intent is hot, and keeps the conversation alive by email afterward. This page covers how each piece works and how to tune it.
BANT lead scoring
Every conversation starts at 0 and accumulates points as the visitor shares signals. The formula is additive, with four dimensions:
| Dimension | Signal | Points |
|---|---|---|
| Budget | Visitor mentions a budget range that meets or exceeds your floor | +25 |
| Visitor confirms budget is available (but no number) | +10 | |
| Visitor has decision-making authority over budget | +5 | |
| Authority | Job title indicates decision-maker (VP, Director, Head, Founder, CXO) | +20 |
| Title indicates influencer (Manager, Lead, Senior IC) | +10 | |
| Need | Stated pain matches your ICP pain description | +20 |
| Evaluating solutions (compared to competitors by name) | +10 | |
| Timeline | Buying within 30 days | +25 |
| Buying within 90 days | +10 | |
| No timeline mentioned | 0 |
Tiers
| Score | Tier | Default action |
|---|---|---|
| 70-100 | Hot | Offer meeting link + Slack alert to sales. |
| 40-69 | Warm | Ask one more qualifying question, then offer content + follow-up email. |
| 0-39 | Cold | Capture email for nurture; do not alert sales. |
Adjust thresholds and per-signal weights per persona from Personas → [persona] → BANT profile.
Meeting routing
Once a lead crosses your Hot threshold (or whenever they explicitly ask for a demo), Quincer offers available times and books the meeting on the right rep's calendar. Routing follows this order:
- Territory rules first. Match on country, state/region, or company size.
- Round-robin within the matching rep pool, skipping reps who are OOO.
- Fallback to the team's default calendar if no territory matches.
Configure territories under Playbook → Routing. You can scope rules by any combination of: country, region, employee count, industry, visitor URL, or persona.
Calendar sources
Meetings are booked via whichever calendar integration is connected:
- Calendly — the widget shows the next few available slots inline, visitor clicks to book.
- Google Calendar — Quincer checks the rep's free/busy directly and creates the event with attendee invites.
- Microsoft 365 — same as Google, with Teams meeting links attached automatically.
If more than one is connected, Quincer prefers the calendar explicitly assigned to the routed rep.
Email follow-up
When a conversation ends (visitor closes the widget or 30 minutes of inactivity), Quincer can send a follow-up email. There are three modes:
| Mode | When to use |
|---|---|
| Off | You handle all outreach yourself. |
| Auto-send | Quincer composes and sends the email automatically via your connected Gmail or Microsoft 365 account. |
| Drafts for review | Quincer creates a draft in your mailbox; you review & send. |
The email is personalized with the visitor's name, the specific pain they described, any tools they mentioned, and a clear next step (meeting link, content, or reply ask).
Cadence
Multi-touch follow-up is available on Growth and Scale. You can configure up to 5 touches over 21 days, with branching based on whether the lead replied or booked.
Escalation to humans
The agent hands off to a human when any of these fire:
- Visitor explicitly asks to talk to a person.
- Score crosses a threshold you've marked as always human.
- Topic falls under a persona boundary (legal, billing, refund, etc.).
- Agent confidence drops below a configurable floor.
See Live chat for how the human takeover works.
Where to tune it
- Playbook → BANT profile — per-persona weights and thresholds.
- Playbook → Routing — territory and round-robin rules.
- Playbook → Email follow-up — on/off, mode, and cadence.
- Playbook → Escalation — which signals trigger a handoff.