agent37
Changing a customer-communication platform should begin with an inventory, not a cancellation button. Your business may have numbers, contact records, workflows, and links tied to the current setup. Map those dependencies before choosing a cutover date.
Read your own agreement and renewal dates
Use the contract and order form your business actually signed. Check the notice process, renewal date, cancellation requirements, and any separate services. A public pricing page is not a substitute for your account’s written terms.
Podium’s public pricing page asks visitors to contact sales for pricing. That does not establish the price or contract length for every customer. Compare your written quote and agreement with the replacement provider’s terms.
- Renewal and notice dates
- Cancellation process and authorised account owner
- Any separate phone, messaging, or payment services
- Access to records after cancellation
- Cutover costs and overlap you approve
Confirm who controls the business number
Write down the number, account owner, current carrier or provider, and the documents needed for forwarding or porting. Confirm whether texting and voice use the same setup and what changes during a transfer.
Keep the old service active until the receiving provider confirms the appropriate cutover steps. Number-transfer timing can vary. Plan the transition around your operating hours and the team available to test it.
Separate contacts, reviews, and workflows
Contact records, conversation history, review links, and third-party review profiles are different assets. Confirm what can be exported and what the receiving system can import. Do not assume a contact export includes every message, attachment, or permission record.
Review your Google Business Profile ownership and review-request links separately from vendor-hosted content. Keep approved contact preferences with the records they belong to, and avoid importing data you no longer need.
- Contacts and the fields your team actually uses
- Contact preferences and opt-out records
- Conversation records needed for ongoing work
- Google profile ownership and review links
- Routing rules, templates, and escalation contacts
Test integrations with a representative request
List each platform connected to the current workflow: field-service software, dealer CRM, practice scheduler, payment provider, and calendar. Ask the new provider to confirm support for the exact actions you need.
Test a new enquiry, an existing customer, a booking request, and a handoff that needs staff approval. Verify the resulting record in the system your team uses. An integration logo does not prove that every workflow is available.
Agree on the rollout and review window
Choose a small first route if that makes the transition easier. Overflow or after-hours coverage can let your team inspect the new intake and handoff before moving more calls.
Agent37 offers month-to-month plans and aims for a 24-hour setup once business details and approved rules are ready. Complex integrations and carrier transfers can take longer. Agree on your specific timeline before making changes to the existing service.
Sources & further reading
These guides explain practical workflows. Product setup, supported integrations, and usage terms are confirmed for your business before you start.
