Fetchit

Switch to dark theme

Phone systems

Configuring the phone system

Set the clinic up with their phone provider so Fetchit can watch for incoming calls, and collect the credentials Orion will need.

Which provider page to follow, and what each one leaves you holding for the Orion step.

  • phone system
  • voip
  • webhook
  • api
  • provisioning
Author
Schultz Technology IT
Owner
Schultz Technology
Updated
Applies to
Fetchit 1.4.0 to 1.6.0
Reading time
2 min
Level
intermediate
For
IT technicians
Prerequisites
Provider portal access for the clinic

Before Fetchit is installed anywhere, the clinic's phone system has to be configured in the provider's portal so Fetchit can watch for incoming calls and raise its popups. Each provider does this with an API or a webhook.

Follow the page for the provider the clinic uses. Every one of them ends with credentials or an identifier that you enter in Orion when you create the phone system worker, so keep what you collect to hand.

Supported providers

  • CoreDial (Clear Voice). A Fetchit user in the ClearVoice portal. Leaves you a username and password.
  • White Label Solutions. A webhook pointed at Fetchit. Leaves you nothing to enter beyond the client itself.
  • Ring Central. A JWT token from the developer portal. Leaves you the token.
  • Skyswitch. Either an API user and domain name, or a SIP extension registered in the PBX.
  • Anything else. A CallerID Vertex box on the clinic's network. No provider configuration and no phone worker in Orion.
Multiple locations

A clinic with more than one site usually wants popups to appear only at the location that took the call. On Clear Voice that needs extra setup; see clinics with multiple locations.