GreetKeeper + SalesCrew

Every inbound call gets answered and booked, then summarised, and the caller lands in your database as a contact, a lead or a booked meeting.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

  • Signed webhook, one POST per call
  • Lead, meeting and call summary written
  • Reply timer starts when the call ends
app.salescrew.io/settings
Settings: MCP tokens, integrations and the audit log

The short answer

  • GreetKeeper answers every inbound call at any hour, books into your calendar, and transfers to your team when a caller asks. It captures the caller's name, number and reason for calling. When the call ends it posts one signed webhook to your SalesCrew instance.
  • SalesCrew matches the caller on phone number or email and creates the contact if it's new. It logs the call, the short summary and the transcript link on your timeline, and records an inbound lead with GreetKeeper as its source. A booking becomes a meeting with reminders.
  • Nothing is looked up during the call. The webhook fires after the event and carries an HMAC-SHA256 signature that your instance verifies before it writes anything. If SalesCrew answers with anything but a 2xx, GreetKeeper retries with backoff.

How it works

Four steps from a ringing phone to a record your team can act on.

  1. 1

    The call is answered

    Your existing number forwards to the dedicated local number GreetKeeper gives you, and GreetKeeper answers the moment the call arrives. Robocalls and silent callers are dropped before the greeting and don't count toward your plan.

  2. 2

    GreetKeeper does the front-desk work

    It answers the questions you trained it on and reads the name, number and time back before it books. When the caller asks, it transfers to your team, and it texts the on-call person the caller's details.

  3. 3

    One webhook per event

    call.completed, booking.created, message.taken or transfer.made posts to the endpoint on your instance as JSON. Its payload carries the caller's name and number, plus their email and address when given. It also carries the reason for calling, the intake answers, the outcome, the summary and a link to the transcript.

  4. 4

    SalesCrew writes the record

    SalesCrew matches or creates the contact and logs the call with its summary. Your inbound channel gets the lead with its source, a booking becomes a meeting and a message becomes a task. The untouched-inbound timer starts on the new lead.

What syncs

Each GreetKeeper event, what SalesCrew writes from it, and what happens next.

GreetKeeper eventWhat SalesCrew writesDirectionObjectsThen
call.completedYour contact, matched on number or email or created; the call logged with outcome, summary and transcript linkGreetKeeper → SalesCrewContacts, calls, timelineInbound lead recorded with GreetKeeper as its source
booking.createdMeeting at the booked time on your contactGreetKeeper → SalesCrewMeetings, contactsReminders by SMS and email at 24 hours and 2 hours
message.takenTask for the person or pool you route to, with the caller's reason and intake answersGreetKeeper → SalesCrewTasks, contactsUntouched-inbound timer starts
transfer.madeCall logged with the transfer as the outcomeGreetKeeper → SalesCrewCalls, timelineNothing more; your team already has the caller
Intake answersQuestion and answer pairs stored on the call and mapped to the custom fields you chooseGreetKeeper → SalesCrewCalls, custom fieldsSegments filter on them
Signature and retriesHMAC-SHA256 header checked before anything is written; a non-2xx answer is retried with backoffInternalWebhook deliveriesFailed deliveries show in your log
AttributionSource and the GreetKeeper number recorded on the leadInternalLeads, marketing tablesYour cost per booked call by channel is a query

Events and payload fields as of September 2026, from GreetKeeper's published webhook contract; GreetKeeper prices from greetkeeper.com/pricing.

On the GreetKeeper side

SalesCrew and GreetKeeper are both built by Hashlogics, so the webhook one side sends is the payload the other side expects. GreetKeeper's own pages cover the receptionist itself. Read the GreetKeeper home page for what it does on your calls, then the GreetKeeper webhook contract for every event and field. GreetKeeper pricing prints the overage rate on each plan.

Setup

A number, an endpoint, a secret, and one real call to prove it.

  1. 1

    Turn on GreetKeeper

    Start the 14-day trial on greetkeeper.com with every feature on and pick the area code for your dedicated number. Then forward your existing number to it at your carrier.

  2. 2

    Copy the endpoint from SalesCrew

    Settings → Integrations → GreetKeeper shows the inbound URL for your instance and the signing secret. The secret goes into GreetKeeper's webhook settings; SalesCrew keeps its copy in Vault.

  3. 3

    Point GreetKeeper's webhook at it

    In GreetKeeper, set the webhook URL and choose the events. Pick all four, or only the ones you route on; a shop that wants bookings alone can send booking.created and nothing else.

  4. 4

    Place one real call

    Ring the number, book a slot with a spare email, then open the contact in SalesCrew. The call, the summary, the meeting and the lead source should all sit on one timeline.

Questions

Does the CRM get the whole transcript?
The webhook carries the short summary and a link to the transcript, and SalesCrew stores both on the call. Your team reads the summary on the timeline and in the daily digest, and opens the link when they want every word.
What if my team was already on the call?
A transfer.made event logs the call with the transfer as its outcome, so your record shows who took it and when. Nothing is duplicated: the match runs on the caller's number, and a second call from the same person lands on the same record.
Can I route a new lead to a person?
Yes. A message.taken event creates a task for you. The speed-to-lead actions assign it round-robin, escalate it if it sits untouched, or queue an AI call-back through your approval queue. GreetKeeper has already texted the on-call person the caller's details by then.
What does GreetKeeper cost?
Starter is $49 a month for 200 answered calls, Professional $149 for 750, and Scale $349 for 2,000. Each plan prints its overage: $0.45, $0.35 and $0.25 per call. Booking is included on every plan, and every plan starts with a 14-day trial with every feature on. Prices as of September 2026 on greetkeeper.com/pricing.
Which SalesCrew plan do I need?
Any tier, from Core at $299 a month with unlimited seats; inbound webhooks are included from Core. GreetKeeper is billed on its own account.

Answer the call, then find it on the record

Contact, lead, meeting and summary, written to the database you own the moment the caller hangs up.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.