A 3CX inbound rule can route calls out to GreetKeeper
You already have the tool for this. Inbound rules and office-hours routing send calls to an external number, and GreetKeeper answers on that number.
Caller
“Nobody's in on a Sunday, I know. My tenant has no hot water and I need someone booked for tomorrow morning first thing.”
What happened next
- Property address and tenant name captured, spelled back and confirmed
- Booked 8:00am Monday into the connected calendar as an urgent job
- Summary emailed to the duty manager, with the recording attached
How GreetKeeper connects to 3CX
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| 3CX | Email or webhook |
What 3CX is in this setup
3CX is a phone system you host yourself or run in their cloud. It handles SIP trunks, extensions, digital receptionists and queues, and you configure all of it from the 3CX Management Console.
Inbound rules are where a call's fate is decided. Each DID gets a rule saying what happens during office hours and what happens outside them.
A rule's destination can be an external number, entered with the outbound prefix your trunk expects. That is how 3CX reaches GreetKeeper. Extensions have their own forwarding rules if you'd rather start with one person's line.
Where the call record lands
3CX logs the call and the outbound leg. GreetKeeper holds the conversation.
Your 3CX reports will show the inbound call, the rule it matched, and the external leg. GreetKeeper holds the transcript, the summary and the caller's details.
Delivery goes by email or webhook, whichever you set. Property managers and trades tend to pick email to a duty address. Teams with a ticketing system pick the webhook and create the ticket themselves.
A booking goes straight into your connected calendar, and your 3CX phonebook stays exactly as it is.
Routing 3CX to GreetKeeper
Management Console. Check your outbound rules first, because that is where this usually trips.
Confirm the trunk can dial out
Your outbound rules must allow a call to the GreetKeeper number. Dial it from a desk phone first. If that fails, the inbound rule will fail the same way.
Open the inbound rule for your DID
Find the DID under Inbound Rules. You'll see separate destinations for office hours and outside office hours.
Set the destination to an external number
Choose External and enter your GreetKeeper number, with any prefix your outbound rules require. Save it against the out-of-hours destination to begin with.
Ring the DID from a mobile
Do it outside office hours, or move the hours temporarily. GreetKeeper should pick up. Then read the transcript and check the 3CX log side by side.
Checks for a clean 3CX cutover
External forwarding uses a trunk channel for the whole call. Count your channels before you point your main DID over.
On self-hosted installs, check firewall rules, outbound prefixes and trunk provider settings first. Those three settle nearly every forwarding question.
Place a test call from a mobile after each change and read the transcript in GreetKeeper.
Questions about 3CX and GreetKeeper
Should I use an inbound rule or an extension forward?
An inbound rule if you want the whole DID covered. An extension forward if you're testing on one person's line before committing.
How does GreetKeeper sit next to the 3CX CRM integration?
That connector works between 3CX and your CRM. GreetKeeper delivers its own record by email or webhook, so your CRM can take both.
Can the digital receptionist send one option to GreetKeeper?
Yes. Point a menu option at an external number and use your GreetKeeper number. Callers who pick that option get answered.
Start with the out-of-hours rule
It is the safest rule to change. Two minutes, no card.