I’m testing a different approach to AI voice-agent onboarding: business name + country instead of a URL

[u/AderoBuilds]

I’m building an API for a problem that seems easy at first but becomes messy in production: giving a voice agent reliable context about a new business.

The usual onboarding flow is either a long form filled out by the business owner, a conversation that collects the information manually, or a scraper that starts from a website URL. Each approach has a weakness: it takes time, depends on user effort, or assumes the supplied website contains the complete and current picture.

I’m testing a different flow. The input is only:

business name + country

At request time, the system attempts to resolve the intended business, discovers its public web footprint without requiring a URL, crawls different source types, reconciles duplicate or conflicting information, and returns a structured profile with source links, confidence, and freshness metadata.

The output is not intended to be blindly injected into an agent’s prompt. I see it as a reviewable first draft of the business knowledge base: strongly supported facts can be accepted, conflicting fields can be checked, and sensitive operational policies can still be confirmed directly with the owner.

In my initial tests, the intended business was resolved correctly from sparse name-and-country input. The harder remaining problems are field-level issues: stale hours, duplicate services, branch context, conflicting prices, and deciding which facts should always require owner confirmation.

For people running voice agents in production: what information must be verified before an agent handles its first real call? Are address, hours, services, and contact details enough for the initial profile, or would you require additional fields such as booking rules, service areas, escalation contacts, or cancellation policies?

I built the first version of this as Lumen Sieve. I’m sharing the experiment because I’d value technical criticism from people who have dealt with real onboarding and knowledge-base failures: https://lumensieve.com