Overview

AnswerStack answers the sales calls your team cannot get to. A family calls your inquiry line on a Saturday evening. The assistant picks up in your community's name, says in its first sentence that it is an AI, listens to what they need, answers from facts you approved, and offers two tour times. The prospect, the call log and the tour all land in your CRM before the caller hangs up.

It only answers calls. It never dials out to prospects.

What it does on a call#

It answers straight away
It greets the caller in your community's name, says it is an AI assistant, gives the recording notice, and asks what prompted the call. Returning callers are greeted by name once they confirm who they are.
It listens before it sells
It asks the questions you wrote, one at a time, in your words. It reflects answers back so the caller knows they were heard, and it never re-asks something the caller or the CRM has already answered.
It answers their questions
Care levels, apartments, dining, pets, visiting hours, pricing if you allow it. Every fact comes from your brief, the community's own profile and published prices, or a document you uploaded. If the answer is not there, it says so and leaves it for the tour.
It books, within your rules
Your booking rules decide who gets booked, for how long and with whom. The assistant offers two specific times, confirms the details, books through your CRM, and reads the confirmation back.
It writes everything down
At hangup it saves the transcript, a three-line summary and the collected answers, and writes the call to the CRM as an activity on the prospect.

What it never does#

Warning

These are not settings. They are how the product is built, and no configuration turns them off.

It never	What happens instead
Hides that it is an AI	The disclosure is the first sentence of every call, and it answers truthfully if asked
Invents a price, a promise or an opening	It says it does not want to guess and leaves it for your team
Gives medical, legal or financial advice	It declines and offers a person
Takes card numbers, passwords or ID numbers	It refuses and says so
Keeps a caller from a person	"Let me talk to someone" works at any point in the call
Dials a prospect	Inbound calls only
Handles an emergency itself	It tells the caller to call 911

How a call goes#

flowchart TD
  ring([Caller dials your number]) --> route{Number has a<br/>published playbook?}
  route -- no --> notinservice[A short 'not in service yet' message]
  route -- yes --> greet[Greeting: AI disclosure,<br/>recording notice, opening question]
  greet --> lookup[(CRM lookup by caller ID<br/>runs in parallel)]
  greet --> discover[Questions from your playbook]
  discover --> consult[Answers from the brief,<br/>the profile and your knowledge]
  consult --> discover
  consult --> rules{Booking rules}
  discover --> rules
  rules -- book --> slots[Two open times offered]
  slots --> booked([Tour booked in your CRM])
  rules -- reschedule --> move([Existing tour moved])
  rules -- transfer --> human([Passed to a person])
  rules -- callback --> callback([Callback captured,<br/>your team notified])
  rules -- redirect --> redirect([Polite redirect line])
  booked --> wrap[Recap, thanks, hang up]
  move --> wrap
  wrap --> log([Transcript, summary, CRM activity,<br/>usage recorded])
  human --> log
  callback --> log
  redirect --> log

A request for a person jumps straight to the transfer step from anywhere in the call.

What you control#

Everything the assistant says and does comes from a playbook you write in the app. Changing it is a publish, not a software release. You control:

Its voice and manner

The name it gives, the company it works for, the tone, and which stock voice callers hear.

What it knows

A written brief, each community's own facts, and documents or web pages it can search.

What it asks

Your questions, in your words, in the order you want them.

Who gets booked

Sentence-style rules that decide the meeting type, its length and who gives it.

What you need before you start#

A phone number for each community. Your AnswerStack account manager buys these and assigns each one to a community; you choose which playbook it runs.
A CRM connection. Every account starts with a private sandbox CRM full of sample data, so you can build and test before you connect your real WelcomeHome account.
For each community: its address, opening hours, when tours can be booked, who gives them, and a human backup plan.

Next: the Quickstart takes you from a new account to an answered test call, or read Key concepts first.