Do I have to change how I work?
No — keep using Salesforce. KwickPhone answers the calls and sends the order, booking or lead into Salesforce, where your team already works.
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 the call data if Salesforce is down or the API is unreachable?
KwickPhone still answers the call, captures the full summary, and holds it locally. When Salesforce comes back online, the queued records sync automatically, so nothing is lost during an outage. You can also see the same summaries in your KwickPhone dashboard regardless of Salesforce's status.
Can each location send its calls into a different Salesforce workspace or channel?
Yes. You can map each phone number or location to its own destination in Salesforce, so a lead from one branch lands in that branch's channel or pipeline. Routing rules are set per number, and you can change the mapping without re-recording anything.
If we stop using KwickPhone later, do we keep everything already in Salesforce?
Every record KwickPhone creates lives in your Salesforce account under your ownership, so it stays exactly where it is if you disconnect. Turning off the integration stops new records from being sent but removes nothing that already synced. You can also export your call summaries from the KwickPhone side before leaving.
How much of Salesforce does the integration get access to, and what stays manual?
KwickPhone requests only the scope needed to create and update the records it writes, not full account control, and you approve that scope during setup. It does not read your unrelated Salesforce data or act on existing records unless you configure it to. Judgment calls like quoting a custom price or approving a discount stay with your team.
