Law firm calls answered, with the intake sent on to Smokeball
GreetKeeper takes the call and runs your intake. A signed webhook carries it to Make or n8n, and your scenario passes it to Smokeball.
Caller
“My mother passed last month and nobody can find her will. I think I'm the executor. Do I need a lawyer for probate, and can I talk to one this week?”
What happened next
- Captured the caller's name, number, email and the name of the estate
- Asked your intake questions about the matter type and key dates
- Emailed the transcript and summary to intake and posted the call to your webhook
How GreetKeeper connects to Smokeball
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| Smokeball | Email or webhook |
What Smokeball is, and how the call reaches it
Smokeball is practice management software for small law firms. Matters, documents, email, calendars and time recording sit together, so the file for a probate or a family law case lives in one place.
The link to GreetKeeper runs through an automation tool your firm already uses or can add. Make's Webhooks module or n8n's Webhook node catches GreetKeeper's call record, and the steps after it hand the intake to Smokeball.
This route suits firms that like to control their own data flow. You decide exactly which fields travel, and your IT partner can read every step.
What arrives from each call
Every call reaches your firm twice: as an email to intake and as a signed webhook your automation can act on.
The webhook fires on four events: a finished call, a booking, a message taken and a transfer. Each one is a JSON POST to the address you set. An HMAC-SHA256 header signs it, so your scenario can check it came from GreetKeeper.
Inside it you'll find the caller's name and number, their email and street address when they gave them, and the reason for calling. Your intake answers come as question and answer pairs. The short summary, any requested time, the outcome and a transcript link sit beside them.
If your endpoint doesn't return a 2xx, GreetKeeper retries with backoff. A busy afternoon on your automation server won't cost you a prospect.
Sending GreetKeeper calls to Smokeball
Plan this with whoever looks after Smokeball at your firm. The GreetKeeper side takes two settings.
Write your intake questions
Matter type, the other party, key dates and how the caller found you. GreetKeeper asks each question on every call and reads the name and number back.
Create the webhook in Make or n8n
In Make, add a custom webhook with the Webhooks module. In n8n, add a Webhook node. Either one gives you an address to paste into GreetKeeper's webhook setting.
Build the steps that reach Smokeball
Add the HTTP or app steps your Smokeball setup uses after the trigger. Map the caller, the summary, the intake answers and the transcript link into them.
Check the signature, then test
Have the scenario verify the HMAC-SHA256 header. Then call your own line as a prospect and follow the record from GreetKeeper through to Smokeball.
Running intake calls for a Smokeball firm
Turn on GreetKeeper's AI disclosure so callers hear at the start that they're speaking with an AI. Law is a regulated occupation under Utah's AI Policy Act, which asks for that notice out loud.
Keep the intake email switched on alongside the webhook. Your intake team gets every call in their inbox, whatever the automation is doing.
Set a transfer for callers with a court date this week. GreetKeeper puts them through and tries a second number you nominate if the first doesn't pick up.
Questions about Smokeball and GreetKeeper
How does GreetKeeper connect to Smokeball?
Through GreetKeeper's webhook. Make's Webhooks module or n8n's Webhook node catches each call, and the steps you add after it pass the intake to Smokeball.
Is the webhook secure enough for client intake?
Each webhook is signed with an HMAC-SHA256 header, so your scenario can confirm it came from GreetKeeper before it acts. It's sent to the one address your firm sets.
What if our automation is down when a call comes in?
GreetKeeper retries the webhook with backoff on any non-2xx response. The call is also in your GreetKeeper log and your intake inbox, so nothing about it is lost.
Can GreetKeeper book consults while it's routing intake?
Yes. It books into a connected Google Calendar or Outlook calendar. Each booking fires its own webhook event, so your scenario can record it in Smokeball too.
Hear it take an intake call
Give it your intake questions and ring it as a new client. 14 days free, every feature on, no card.