Do I have to switch off Service Fusion?
No. Keep Service Fusion exactly as it is — KwickPhone works alongside it, answers the calls, and hands your team the booked job to enter.
Can it take payment on the call?
Yes — fully PCI-compliant. It charges a card on file or takes a new one, and no one reads a card number out loud.
How long does setup take?
Minutes. Sign up yourself and set it up by talking — no website or typing required.
What happens to a call if Service Fusion is down or the API is unreachable when someone calls?
KwickPhone still answers the call, collects the caller's details, and confirms the appointment with the customer. The job is queued and written into Service Fusion automatically once the connection is restored, and the office is notified so nothing is lost during an outage.
How quickly does a booked call actually appear as a ticket in Service Fusion?
In normal conditions the job is created in Service Fusion within seconds of the call ending, so it's visible to dispatch almost immediately. If Service Fusion is slow to respond, the record is retried in the background until it lands, and the office sees a status note in the meantime.
We run three locations — can calls route to the right Service Fusion account and dispatch board?
Yes. KwickPhone can map each phone line, service area, or business unit to the correct Service Fusion location so the job is created against the right board and territory. Techs, service types, and availability are read per location, so a call for one branch doesn't book against another's schedule.
What access does KwickPhone have inside Service Fusion, and what if we switch away later?
KwickPhone connects with scoped credentials limited to reading availability and customer records and creating jobs and contacts — it doesn't need full administrative control. The data lives in your Service Fusion account, which you own, so if you disconnect KwickPhone the tickets and history already written stay in Service Fusion untouched.
