Home-service buying guide
Keystone Answering Service: Define the Account and the Work You Are Buying
For a home-service business with more than one office, an answering quote must describe more than the number of incoming calls. It should explain which location the service represents, who receives the request and what work happens with your staff after the caller hangs up.
Updated · Published by Revo
Keystone Answering Service’s published FAQ provides useful starting points for that discussion. Published by Revo, a competing AI receptionist provider. Official information reviewed October 30, 2026. This is a documentation review, not a firsthand service test.
Separate location accounts from billing assumptions
Keystone’s official FAQ says each location has its own account, answering phrase and handling instructions. It also says pricing depends on agent time working with callers and the client’s staff. The FAQ does not publish a complete dollar tariff or establish whether multiple locations receive separate invoices, pooled usage or common discounts.
Those unknowns belong in the proposal. Separate accounts can organize different instructions without telling you how the supplier combines charges. Do not build a per-location budget from the account description alone.
Consider an illustrative repair business with a main office and a second branch. The same company name does not mean both branches accept the same requests, serve the same addresses or use the same callback team. Document those differences before asking the service to answer either location.
Build a location-account map
Use one row for each actual account the provider proposes. Keep responsibilities concrete enough that the office can check a message against them.
| Field | Main office | Second office or service branch |
|---|---|---|
| Account identifier | Provider-confirmed identifier | Provider-confirmed identifier |
| Approved greeting | Exact business wording | Exact branch wording |
| Service boundary | Accepted requests and area | Accepted requests and area |
| Required intake | Fields needed for useful follow-up | Branch-specific differences |
| Routine recipient | Person or office role | Person or office role |
| Unavailable recipient | Approved fallback | Approved fallback |
| Instruction owner | Who can request a change | Who can request a change |
| Billing treatment | Written account and usage terms | Written account and usage terms |
This map is a proposed purchasing resource, not proof that Keystone offers particular permissions or account-linking controls. Ask the provider how the map would be implemented and which details appear in its proposal.
For example, a homeowner may contact the wrong branch about an existing appointment. Define whether the service should capture the request, identify the proper office or use a supported transfer. Do not assume a separate account automatically gives an agent access to every branch’s calendar or job records.
Include work with your staff in the usage discussion
An incoming call can create additional communication after the original conversation ends. Because Keystone describes pricing in terms of agent work with callers and staff, ask how each proposed follow-up activity is measured.
Use the same set of scenarios when comparing proposals:
- A new inquiry that requires only a delivered message.
- An appointment question that requires contacting the office.
- A request sent to an unavailable staff member.
- A correction to an on-call destination or staff record.
For each scenario, record the caller conversation, any staff contact and any configuration work separately. Ask which activities are billable and which measurement rules apply. This is not a claim that each listed activity carries a separate Keystone fee.
A provider’s per-minute label does not establish identical measured work across suppliers. Keep any comparison based on each provider’s documented definition rather than reusing another provider’s billed-minute total.
Verify portal updates through a controlled example
The FAQ describes using a web portal to update on-call schedules and personnel information and to deliver messages. It also describes month-to-month agreements with 30 days’ termination notice. Confirm current purchased terms, access and notice procedures directly.
For the portal evaluation, ask an authorized office administrator to show how a proposed change would be made. Check which account it affects, when agents receive it and what happens if instructions conflict. A portal’s existence alone does not establish role-based approvals, version history, instant synchronization or a particular audit export.
| Proposed check | Evidence the office should request | Avoid assuming |
|---|---|---|
| Change one branch’s recipient | Resulting account instructions | Other branches changed too |
| Update a staff record | Provider-confirmed effective information | Every related field updated automatically |
| Review a sample message | Account identity, request and delivery record | Delivery proves business responsibility accepted |
| Remove an old staff contact | Confirmed removal and remaining destination | Every historic record or permission disappeared |
| End service | Applicable notice and effective date | Stopping forwarding ends the agreement |
These are suggested evaluation checks, not tested Keystone performance results. Perform any real changes only through authorized staff and an agreed test process.
Compare Keystone with Revo on the required workflow
Keystone describes live-agent service. Revo provides AI reception, with its current plans listing appointment booking and configured scripts, hours and rules. Revo’s public feature descriptions do not establish Keystone-style location accounts, staff-contact billing or portal controls.
If the office primarily needs supported intake and booking, compare that exact workflow under each proposed service. If it needs external humans performing additional work with staff, keep that requirement explicit. An AI receptionist should not be presented as functionally equivalent merely because both offers answer incoming calls.
Use Revo’s current pricing to check the selected plan and included minutes. Keep launch offers distinct from ongoing list prices and confirm the applicable team-transfer scope before including it in a comparison.
Frequently asked questions
Does a separate Keystone account mean a separate invoice?
The reviewed FAQ does not establish that. Ask for the proposed invoicing and usage treatment for every location.
Is only time speaking to callers relevant to Keystone pricing?
The FAQ also refers to agents working with your staff. Obtain the measurement and included-work definition for the actual proposal.
Does the portal prove that every update is immediate or approved by a manager?
No. Confirm timing, access and any approval process. Those controls are not established by a general portal description.
Does month-to-month mean no cancellation notice?
No. Keystone’s FAQ describes 30 days’ notice. Confirm the current agreement and how to submit a notice; this guide does not determine legal rights.
Obtain a quote your office can operate
Give Keystone the completed account map and follow-up scenarios. If AI reception matches the tasks you need handled, review Revo’s current plans with the same required outcomes and a clearly defined exception owner.
Sources and current terms
Give Keystone the completed account map and follow-up scenarios. If AI reception matches the tasks you need handled, review Revo’s current plans with the same required outcomes and a clearly defined exception owner.
Review Revo’s current features and plans for the workflow your business needs.
Compare plans