Powsoo / Guides / Tap-to-confirm cards vs SMS fallback for voice intake

Tap-to-confirm cards vs SMS fallback for voice intake

Updated 2026-07-13
Use an on-screen card when the caller is on a web session. It confirms the value in the same tab with no phone number required and no carrier round-trip, and it covers any field: emails, phone numbers, dates, and reference codes. Use SMS only when there is no screen, on a pure phone (PSTN) call where the agent has nothing to render into. SMS needs a valid mobile number first, sends the caller out of the call to their messages app, and adds a carrier hop that can lag or fail before the value comes back. That makes on-screen the default and SMS the fallback, not the reverse. Powsoo renders an on-screen card when a web session exists and falls back to SMS when it does not, so the same agent handles web and phone callers without separate logic. The confirmed value returns by webhook either way.

Side by side

On-screen cardSMS fallback
Needs a phone number firstNoYes
Stays in the call flowYes, same sessionNo, caller switches to messages
LatencyInstant renderCarrier round-trip
Works with no screen (PSTN)NoYes

Why on-screen wins for web sessions

SMS was the original workaround because it was the only second channel a phone agent had. It carries three costs: you need a valid mobile number before you can send anything, the caller leaves the conversation to open their messages, and the message rides a carrier round-trip that can lag or drop. For a web session, none of that is necessary.

An on-screen card renders in the tab the caller is already in. They read the value, tap Confirm, and stay in the call. It also covers fields SMS handles awkwardly, such as choosing from a list or confirming a written-out date.

Use both, in order

Powsoo renders a card when a web session exists and falls back to SMS when it does not. You wire the agent once and it handles web and phone callers without branching logic. See the data-capture guide for the full picture, or what a visual layer is for the concept.

Frequently asked questions

Is SMS confirmation worse than an on-screen card?

For web sessions, yes. SMS needs a valid phone number first, sends the caller out of the call to their messages app, and adds a carrier round-trip that can lag or fail. An on-screen card confirms in the same session with a single tap.

When is SMS the right choice?

On pure phone calls with no browser. If the caller reached the agent over PSTN and there is no web session to render into, an SMS one-tap link is the way to get a confirmed value.

Can I use both?

Yes. Powsoo renders on-screen cards when a web session exists and falls back to SMS when it does not, so the same agent handles web and phone callers without separate logic.

Five minutes to zero spelling errors.

Go from zero to live confirmation cards in under five minutes.
No migration required.

Get started Read the docs