What's going on, it's Jonathan.

Before you configure an AI receptionist, write its job description.

One page is enough to start. If the business owner can't explain the job clearly, a longer prompt probably won't fix it.

Here's a practical outline you can copy.

"Help callers request a cleaning estimate. Collect the service needed, property location, preferred contact method, and a short description. Send the request to the office."

That's an example. Replace it with the business's actual process.

List the current hours, service area, services offered, and anything the owner has approved the system to say. Give each item a source and someone responsible for keeping it current.

For prices that depend on the job, spell out the next step for getting an estimate.

Write down what it must not promise: an unconfirmed appointment, a custom price, or a service the business doesn't offer.

Decide what it should do when information is missing.

Who receives the request? What details do they need? What happens outside business hours or if a transfer fails?

Have the owner review this page before you build.

Then use it as your setup brief and test checklist. Compare the software's actual behavior with the agreed job, and fix the gaps before involving customers.

If you want to explore the tools and training for putting an AI agency service together, my free course includes AI software and a setup guide:

Start with the job description. Build around the job.

Let's build. 🦁

Jonathan

Sponsored

AI can draft the PRD and prototype the idea. Jira Product Discovery helps teams decide whether it belongs on the roadmap. Bring feedback and ideas together, prioritize as a team, and keep your roadmap connected to delivery in Jira.

Get Started for Free