phon8 help
This guide covers the phon8 add-on inside ServiceM8 and the separate phon8 phone app that pairs to it.
Open the ServiceM8 add-on
- Sign in to the correct ServiceM8 business account and open Add-ons.
- Turn on phon8 for that account, then open it from Add-ons or a phon8 job action.
- ServiceM8 asks the account to approve phon8 access through OAuth. Check that you selected the intended business account and approve only the requested permissions. If the connection is missing or expired, use Connect ServiceM8 inside the add-on and complete the consent flow again.
Connect calling and messaging
- Open the Twilio tab. The preferred Connect with Twilio flow uses Twilio OAuth; sign in at Twilio and approve the requested access.
- Where Twilio OAuth is unavailable, an administrator can use the displayed credential setup with an Account SID/Auth Token or restricted API key. Enter secrets only in phon8’s secure connection form. Never send them to support.
- Choose which Twilio numbers phon8 may use, assign numbers to active ServiceM8 staff, and choose the allowed call and message channels.
- Review call handling, recording, business hours, missed-call messages and staff access, then save.
Twilio call, number and message usage is billed by Twilio. The separate phon8 subscription is £5/month.
Pair the phone app
- In the ServiceM8 add-on, open Phone app and create a pairing code for the intended active staff member.
- Open the phon8 phone app on the device and enter the code before it expires.
- Choose Sign in with ServiceM8 in the phone app if you need to verify your staff identity, then enter the one-time pairing code it returns to the add-on. Alternatively, enter a pairing code created by an administrator.
- Allow microphone access when you want to make or answer calls. Keep the app open and the device unlocked for incoming-call availability.
Pair each device to the correct staff identity. Revoking or unpairing a device removes its access; it does not delete shared call or message history. The app pairs to an existing ServiceM8 business; it does not create a new business account.
ServiceM8 actions and access
- The add-on can be opened from Add-ons and from phon8 call or Messages job-card actions on supported ServiceM8 surfaces.
- Job actions use the selected job context. Review the displayed job and recipient before calling or sending any message.
- If ServiceM8 reports a missing scope, permission or reconnect error, ask an account administrator to reconnect phon8 and review the requested access. Do not share OAuth tokens or pairing codes.
- AI call tools and messaging actions can create or update ServiceM8 records only when the connected account has the required access and the configured action is enabled.
Calls and recording
- Use Calls for recent call history and call details. Linked-number assignments and Routing determine where incoming calls go.
- Use Record calls under Twilio setup → Call handling to enable or disable call recording. An IVR route can also disable recording for that route.
- When recording is enabled, phon8 shows a notice before a paired phone starts an outgoing call. Make sure you have informed other participants and obtained any permission required for the call.
- Recording retention applies to new recordings. “Keep until manually deleted” does not automatically remove them. Disabling recording does not delete existing recordings.
- Voicemail separately records the caller’s message. AI-routed calls use live transcription so the assistant can respond; disabling call recording does not turn off AI transcription or call transcript records.
Messages
- Open Messages or a job’s Communication action, choose a linked sender and recipient, select Text or WhatsApp, review the text, and send.
- WhatsApp replies require a valid conversation window or an approved template. Twilio must have the corresponding sender and channel configured.
- Message states can include queued, sent, delivered, failed or undelivered. “Queued” means Twilio accepted the request; it does not prove delivery. Refresh the conversation to see later status updates.
- If phon8 says the send outcome is uncertain, refresh the conversation before trying again so you can check whether the first attempt arrived.
AI and ServiceM8 actions
- AI call agents and tools are configured under AI agents. Review each agent’s greeting, instructions, voice, model and enabled tools before routing calls to it.
- AI-written customer messages are drafts for staff review. Check names, dates, prices and other details before sending.
- ServiceM8 job, customer and task actions may create or update business records. Review the proposed details and confirm only when they are correct.
- phon8 does not collect payment from your customers. Customer payment actions are unavailable.
Troubleshooting
- Twilio is not connected: reconnect the correct Twilio account, confirm it has an active number, then link that number in phon8.
- Call will not start: check microphone permission, internet access, the selected caller ID, staff access and Twilio balance/configuration.
- Incoming calls do not ring: keep the paired app open and device unlocked; check the number’s route, staff assignment and paired-device status.
- Message failed or remains queued: check the sender’s SMS/WhatsApp capability, recipient format, Twilio account status and WhatsApp conversation window. Refresh for the latest delivery state.
- ServiceM8 data is missing: reconnect phon8 to the intended business account and check that the signed-in staff member has the required access.
- Phone app will not pair: check the business and staff selection, create a fresh unexpired code in the add-on, and enter it once. Revoke an unknown device from the Phone app device list.
- Twilio connection is missing: check the Twilio account and number assignment; reconnect using Twilio OAuth or have an administrator replace expired credentials.
Contact support
For help, email info@adamsaddons.me.uk or use the support page. For a privacy request, contact support and say which privacy right you want to exercise; do not include unnecessary personal information. Include the time of a technical issue, the screen you were using and any non-sensitive error text. Do not email passwords, access tokens, Twilio secrets, pairing codes or customer message contents.