A modal per phone line covering forward targets (up to six, pickable from the team list), ring timeout, voicemail on/off and greeting, missed-call text-back on/off and wording, inbound recording with its announcement, outbound recording as a separate decision, and whether the line rings in the app.
Also called: set up call forwarding · voicemail greeting · how long should it ring · phone settings
- 1Saves the whole VoiceConfig via PATCH /api/comms/numbers; the webhook acts on it from the very next call with no re-provisioning
- 2Picking a team member fills BOTH their name and their own phone from their account record (migration 268)
- 3The number in the box is what rings — changing that person's profile later does not silently re-route a configured line
- 4Someone with no number on file is labelled as such in the picker rather than looking identical to everyone else
- 5sanitizeVoiceConfig bounds everything on read and write, so stored config is always something the webhook can act on
Phone systems are configured with vocabulary — hunt groups, failover, extensions — that a builder has no reason to know, and getting it wrong means calls silently going nowhere. Each line now asks three plain questions instead: who should it ring, for how long, and what happens if nobody answers, plus recording and text-back. Teammates are picked from a list rather than by typing a cell number from memory, and the number the line stores stays authoritative so an edit to someone's profile cannot quietly redirect a business line.
- Phone configuration written in carrier jargon
- Forwards saved to numbers that go nowhere
- No control over ring time or greeting
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →