Getting your team comfortable with it
If somebody on your team answers the phone for a living, they will have one question when you announce this, and they will probably not ask it out loud. Everything about how this goes depends on whether you answer it in the first sentence or leave it hanging for a fortnight.
Say the thing they are worried about
If their job is not at risk, say so plainly, first, before explaining anything else. Leading with features and getting to job security in week three is how you lose someone competent to a business down the road. And if the honest answer is that roles will change, say that instead — people handle a straight answer far better than they handle a fortnight of inference from your tone.
What actually changes for them
The calls that stop arriving are the ones that broke their concentration mid-task: hours, prices, parking.
Which is the part good front-desk staff are most frustrated by.
The ones needing judgment, which are the interesting ones.
Reviewing summaries, spotting what it got wrong. Small, but real — do not pretend it is nothing.
Make them the expert, not the subject
The person on your desk knows exactly which questions come up and precisely where callers get confused, and no amount of configuration substitutes for that. Ask them what it should say about your most awkward price, and give them the job of flagging bad answers. Someone who is asked to fix a thing behaves very differently from someone it is being done to — and in this case the request is genuine, because they really are the best source you have.
The first fortnight
Expect some wariness and a certain amount of "it did not say that right". Take each one seriously and fix what is fixable, because those reports are free quality control from your most informed critic. The tone usually turns the first time it handles a Saturday morning nobody could have covered — at which point the argument is over without anybody having to concede anything.
Frequently asked
Answer the job-security question first and plainly, before anything else. Leading with features and reaching it in week three is how you lose a good person.
Say so. People handle a straight answer far better than a fortnight of inferring it from your tone.
Fewer interruptions from routine calls, customers at the desk no longer being interrupted, more of the calls that need judgment — and a little new admin reviewing summaries.
Give them the job of finding bad answers and deciding what it should say. They know where callers get confused better than any configuration screen does.