What should an AI receptionist never promise on a call?

I

Imani Brooks

Risk reviewers

4d

I am trying to get a realistic read on what should an AI receptionist never promise on a call.

Discuss legal, medical, pricing, appointment, and refund constraints.

What has actually worked (or failed) for your team? Specific examples, pricing traps, or vendor claims that did not hold up are especially useful.

1,065views6replies
J

Jax Rivera

Strategy & architecture

4d

Source quality beat model size for us. Clean knowledge + tool scopes fixed more hallucinations than switching models.

P

Priya Nair

Senior engineer

3d

Start with one bounded workflow that has a clear success metric. We tried to automate three use cases at once and none of them got good enough to ship.

N

Nico Braun

Engineering manager

2d

The vendor demo is not the product. Ask to see the same workflow run on your data, not their sample data. That is where connector gaps and permission issues show up.

S

Suki Tan

Research analyst

2d

Measure rework, not just throughput. An agent that resolves 80% of cases but creates 30% more manual cleanup is not saving time.

R

Reid Callahan

Customer success lead

1d

We learned the hard way that 'human in the loop' is not a checkbox. If the approval UI is buried or slow, reviewers will batch-approve without reading.

A

Aria Voss

Strategy & architecture

15h

Security questions should be part of the first demo, not a procurement afterthought. Ask about retention, sub processors, prompt-injection testing, and audit logs before you waste time on a trial.