Beardbrand founder shares AI phone support build

Beardbrand founder Eric Bandholz says his team built an AI phone support service in about two days and made it the brand’s main support line. His 10 October account offers an example of a merchant connecting voice software to store operations, with customer verification becoming a central part of the build.

In his original walkthrough, Bandholz describes xAI voice, Shopify orders, Recharge subscriptions and a Cloudflare Worker between the agent and store. He says that intermediary keeps Shopify credentials out of the voice agent.

What the founder says it handles

Reported tasks include order updates, changes to unshipped orders and subscription management. Phone purchases become draft orders with checkout links sent by email. Requests the agent cannot finish are passed to the team by email.

Bandholz also describes an early test that exposed customer information incorrectly. He says the revised flow checks identity and requires an emailed code for private details or changes, with repeated verification failures blocked.

These are the founder’s descriptions, not independently audited security controls. We have not inspected the implementation or tested the support line. His post’s attached video could not be played during our review.

What merchants can take from it

Our recommendation is to define the service before choosing its voice: which questions it may answer, which records it may access, which changes require verified identity and how an unresolved request reaches a person.

A useful pilot would measure completed requests, incorrect answers and successful human handoffs, alongside the time spent reviewing calls. A short build time alone does not establish lower support costs or better customer outcomes.

For a team considering similar automation, use a small set of permitted tasks and review test results before expanding access. Ask the implementer to demonstrate that verification is enforced by the service handling requests, rather than relying only on conversational instructions.

For a separate example of reviewing an agent’s work and permissions, see our Moby Automations checklist.