SimpleTalk migration
Move from SimpleTalk
to Lippy
The login is gone. Keep the calls, the calendar, and the number you still control. Start with one workflow, test a real call and a real booking, then switch.
Updated October 15, 2026.
The order that avoids a dropped call
Sixstepsbeforeyoumovetraffic
Do them in this order. Rebuilding the agent before the live number has a fallback is how customers get silence, or the same outreach twice.
- 1
Cover today's calls
Call the business number and write down what the caller hears. If it is failing, point a number you control at a person before you rebuild anything. Name a person for urgent callbacks and for appointments that are still unconfirmed.
- 2
Use the records you still have
The login is gone. Prompts, recordings, and queues that lived only in SimpleTalk are out of reach for now. Pull the next two weeks of appointments off the calendar you still open, contacts and notes out of GoHighLevel or your CRM, and the last invoice out of email. Write down hours, services, and transfer rules from the people who approved the script.
- 3
Confirm what you already control
The carrier account, the forwarding, the GoHighLevel location, and the calendar are what make a move possible. If SimpleTalk issued the number under its own carrier account, the carrier may deal only with that account holder, which now runs through the bankruptcy trustee. Ask the carrier what it needs. The Chapter 7 filing alone does not move a number to a new vendor.
- 4
Map one workflow
Bring the hours, services, transfer rules, and calendar access your team still has. Lippy stands up the first job: answer, book into the live calendar, text back when a call is missed, and transfer when a person is needed. Everything else waits.
- 5
Test before you switch
Place one inbound call from a phone you control. Confirm the booking or the CRM note actually landed. Send or receive one text. Do not turn outbound back on until you know which customers were already contacted.
- 6
Cut over with a fallback
Move the number by forwarding or SIP when you control it. Keep a person or the previous route available until the new path has taken a real call. Then move the next workflow. Stop if a test booking does not show up where your team works.
What the move actually needs
Whatyoubring,andwhatLippyruns
What you bring
- Hours, service area, FAQs, and transfer rules your team still has
- The calendar and CRM access your business is allowed to share
- Each phone number, and who controls the carrier or forwarding
- Upcoming appointments and open callbacks, with a person named for each
- A list of outreach already queued, so a switch does not call the same customer twice
What Lippy sets up from that
- Inbound answering on the number you control, by forwarding or SIP
- Booking, rescheduling, and canceling against live calendar availability
- Missed-call text-back, plus SMS and email on the same conversation
- A transfer to your team when the call needs a person
- A connection to tools you already run, including GoHighLevel
SimpleTalk migration FAQ
Commonquestions
Lippy AI
Start with the number
that has to stay up
Book a demo and tell us which workflow has to stay up. Bring the calendar, the CRM, and the last invoice.