Vivollo
Demo

Live Handoff

Humans, exactly when it matters.

Vivollo resolves the routine and knows when to step back. When a conversation needs a person, it hands over the full thread, memory and customer context in real time — then quietly resumes once the human is done.

Request a demo
handoff

  1. AI handling

    Resolved 2 routine chats this thread.

  2. Escalation triggered

    Refund request over your auto-approve limit.

  3. Agent notified

    Pending → routed to an available agent · 8s.

  4. Maya took over

    Stepped in with everything already loaded:

    context handed over
    historymemorycustomercart

AI resumes the thread once Maya is done.

The moment a person takes over.

Most bots hand over a blank screen. Vivollo hands over the thread, the tools it ran and what it already promised — so your colleague answers instead of asking again.

A typical bot
I want to return order #10482 — it's 4,200 TL.Transferring you to an agent. Please hold.Maya · supportHello! How can I help you today?
Vivollo
I want to return order #10482 — it's 4,200 TL.Handed to the team · refund over limit · context attachedMaya · supportHi Elif — I've approved the return on #10482. The refund goes back to your card within 3 business days.

01Desk

The customer sees one conversation. So does your team.

The assistant checks the policy, sees the refund is over its limit and hands the thread to a person — with the order, the memory and the tool results already in the rail.

FIG 1What the customer sawPanel · what Maya saw
handoff
I'd like to return #10482, 4,200 TL.check_policy→refund > 2,000 TL limitI'll get a colleague to approve that — they have everything already.Handed to the team · 8 sMaya · supportApproved — the refund is on its way to your card.Assistant resumes when Maya is done
The inbox details rail: session, activity and the customer's other conversations
Nothing repeated
The thread, the tool calls and the customer record travel with the handoff.
Real time
Pending, then assigned to whoever is free — on your desk or in Vivollo's inbox.
Resumes
When the person closes it, the assistant picks the thread back up.

02Rules

You decide when a person steps in.

A refund over a limit, an angry customer, a VIP, a plain “let me talk to someone”. The rules are yours; the assistant handles everything else.

  • Triggers

    Value thresholds, sentiment, an explicit request, VIP routing.

  • Context

    History, memory, the customer and order record — carried over, not summarised away.

  • Resume

    One conversation throughout: none → pending → active → ended, then the assistant again.

Handoff rules · Nordvik front door
  • Refund over 2,000 TLhand off
  • Sentiment: angryhand off
  • Customer asks for a personhand off
  • VIP segmentpriority

Handoff states

  1. none
  2. pending
  3. active
  4. ended

Proof of control

An escalation, with the context carried.

The refund is over the limit. The assistant does not guess: it marks the thread pending, notifies the team with everything attached, and steps back in when Maya is done.

  1. 1detect_intent180 msInput'return #10482'refund · 4,200 TL
  2. 2check_policy40 msInputrefund limitlimit 2,000 TL · over
  3. 3handoff25 msInputpending · context attachedteam notified · history, memory, order
  4. 4assign8 sInputMayaactive · took over
  5. 5resume10 msInputended → assistantthread continues
Example conversation; latencies are illustrative.

Connected channels and stores

All integrations
  • WhatsApp
  • Instagram
  • Web widget
  • ConnexeaseConnexease
  • GrispiGrispi
  • Zendesk

Works well alongside

Agentic AIActs on real data — tools, memory, resolution.Unified InboxEvery channel in one inbox — context follows the customer.Conversation IntelligenceSee why customers reach out — trends and gaps.

Ready to meet your AI agent?

Book a demo and we'll build a working agent on your real data — across WhatsApp, Instagram and your website. Live in days.

Request a demo