Get Quincer
New ยท Voice (PSTN)

Quincer can now answer the phone

Someone dials your number. Instead of hold music and a menu tree, they get your Quincer agent: same persona, same knowledge, same handoff. Just a different way in.

There is a category of experience so universally despised that it has generated its own genre of comedy: the phone tree. Press 1 for billing. Press 2 for support. Press 3 to hear these options again. Press 4 if you have somehow reached the wrong department. Press 0 repeatedly in the hope that a human will eventually appear. When they do appear, they ask you to hold. You hold. You hold for longer. You hear seventeen seconds of the same saxophone loop. You wonder if you have died.

We are happy to announce that Quincer can now answer your phone number directly, and it does not do any of that.

What "answering the phone" actually means here

Quincer's voice engine has been running on the web since launch. Web visitors can click a button and talk to a Quincer persona. What we have added is a telephony transport layer: the ability to point a real PSTN phone number at that same voice engine, so that anyone with a phone can dial in and get the same agent, without going anywhere near a browser.

The key architectural thing to understand is what did not change. The persona is the same. The knowledge base is the same. The tools (booking, qualification, CRM sync, escalation) are the same. The billing is the same. The guardrails are the same. The only new piece is the front door. The phone caller becomes, in the system's eyes, just another client of the voice engine that happens to have arrived by a different route.

This matters because it means every improvement you make to your Quincer persona benefits all channels simultaneously. You update your knowledge base once and it is current for web visitors, phone callers, and SMS threads alike. You do not maintain parallel versions of anything. There is one agent and multiple ways to reach it.

๐Ÿ“ž
Ringing...
Answers in under 1 second.
AI agent speaking, barge-in enabled. Interrupt and it stops mid-sentence.
animatedPhone rings, Quincer picks up, voice waveform shows the agent live and listening. No hold music. No menu tree. No saxophone.

One detail worth flagging: barge-in is enabled. If the agent is mid-sentence and the caller interrupts to redirect the conversation, the agent stops talking immediately and listens. This is how human conversations actually work, and it is how this one works too. You are not waiting for the agent to finish a paragraph before you can say "actually, I need billing." You just say it.

Carrier options at launch

We are shipping with support for Twilio and Telnyx. Both are well-established PSTN carriers with excellent geographic coverage, and both integrate cleanly with the voice engine. You can provision a new phone number through either and point it at Quincer in a few minutes from the dashboard.

For enterprises with existing telephony infrastructure, the path is bring-your-own. If you already have a number, a contact center, or a PBX that your customers know and use, you can point it at Quincer's endpoint without abandoning the number or the infrastructure. The carrier stays the same. What answers changes.

Your existing phone number becomes the front door. The agent is what answers when someone knocks.

Caller memory: the agent knows who you are

One of the things that makes phone support feel impersonal is the reset. You call in, give your name, explain the situation, get transferred, explain the situation again. With Quincer, the agent maintains caller memory across channels. If this phone number has called before, or interacted with the web widget, or had an SMS conversation, the agent has the history. It knows the context. It does not make you repeat yourself.

For practices, this means a patient calling to reschedule does not have to reintroduce themselves. For software sellers, a prospect who chatted on the website last week and is now calling to ask a follow-up question gets picked up where the conversation left off. This is not magic. It is just not throwing away information you already have, which, for most phone systems, is unfortunately the default.

Human handoff: the warm transfer

The agent handles what it can handle and knows when to stop. When a caller asks to speak to a person, or when the conversation reaches a point where a human genuinely needs to be involved, Quincer performs a carrier warm-transfer: your teammate's phone rings, they pick up, and the caller is connected directly. The agent announces the caller and the context before the transfer completes, so your teammate is not walking in cold.

What happens when nobody picks up is important: the agent does not abandon the caller. It takes a voicemail for the team (so the missed call is captured and actionable), and then it returns the caller to the AI conversation. The caller can keep going. They can book something, get more information, or leave a message. They are not stuck listening to a voicemail greeting and hanging up with nothing resolved. The fallback is not a dead end. It is a branch in the conversation.

๐Ÿ“ž
Caller dials in
PSTN via Twilio or Telnyx
๐Ÿค–
Quincer AI agent
Same persona, knowledge, tools
๐Ÿ™‹
Caller requests human
Or agent triggers escalation
Teammate answers
โœ…
Warm transfer
Caller connected, context handed over
No answer
๐Ÿ“ฌ
Voicemail captured
Team notified
๐Ÿ”„
Back to AI
Caller keeps going
animatedCaller dials in, AI handles it, "request a human" forks: warm transfer on the happy path, voicemail captured plus return to AI on the fallback. Nobody goes nowhere.

Two-way SMS in the same session

Phone voice is the new addition, but it ships alongside two-way SMS as well. A phone conversation can hand off to a text thread if the caller prefers. A customer who called to book an appointment can get a confirmation SMS with the details. A follow-up that started on the web can continue via a text reply. The channels work together because the memory is shared. The agent knows which thread is which and keeps them in sync.

This is how modern communication actually works for most people: a quick call to get oriented, then a text for the confirmation. Quincer does both sides of that without you having to stitch the systems together manually.

The part that did not change

The voice engine, the AI model, the persona configuration, the knowledge base, the booking integrations, the CRM sync, the guardrails: all unchanged. Telephony is a transport, not a product. We added the ability to receive a phone call the same way a TCP server receives a connection. The agent on the other end of that connection is exactly the same agent that has been answering web visitors. It just picks up the phone now too.

What this means for your existing setup

If you have a Quincer agent already configured, adding a phone number is a dashboard setting, not a rebuild. Your persona, knowledge base, and booking rules carry over automatically. You are adding a channel, not starting over.

The phone has not gone away as a communication channel. For a large segment of callers (and for the specific kinds of urgent situations where typing feels inadequate), it remains the first instinct. For a long time, the choice for businesses was: hire humans to staff a phone line, or let it go to voicemail. There is now a third option. The phone line picks up, it knows things, it helps, and when a human genuinely needs to take over, the human is there.

Hold music was never doing any of that.

Give your phone line an agent that never puts anyone on hold.

Point a Twilio or Telnyx number at Quincer and your existing agent starts answering calls. Warm transfer when a human is needed, voicemail fallback, caller memory across every channel.

Add a phone line to your agent โ†’