InPost shipped notification

Example scenario

InPost webhook at 2:02 PM. SMS with code and locker address. BaseLinker status updates without manual clicks.

When it runs

The playbook starts automatically when Coldbot tags a call or event as: “InPost webhook: in transit”. You can narrow filters (location, channel, business hours) without changing the voice script.

• ✓InPost webhook: in transit

What happens automatically

Each step runs in sequence (or in parallel where noted). No copy-paste between voice AI, SMS gateway, and CRM.

• ✓SMS with parcel locker code
• ✓Optional voice outbound
• ✓BaseLinker update

What you configure

Tunable during onboarding — copy, thresholds, and channel priority:

• ✓Pickup code template
• ✓First status change only
• ✓GDPR aware

Recommended integrations

Native connectors or Zapier/Make/webhooks. Status “coming soon” means we enable it on request during rollout.

• ✓InPost
• ✓SMSAPI
• ✓BaseLinker

Works with voice templates

Deploy these agent scripts together with the playbook — same disposition tags power both sides:

• ✓Local Retail Pickup

Onboarding checklist

We configure this playbook during Coldbot setup — usually in one working session:

• ✓Map disposition tags from your voice script
• ✓Connect integrations (OAuth or API keys)
• ✓Test SMS/e-mail copy on a sandbox number
• ✓Dry-run on 3 sample calls before go-live
• ✓Enable monitoring webhook + weekly report

Zapier / Make recipe

We export a starter automation: Coldbot webhook → your stack. Field mapping is done in onboarding.

• ✓Trigger: call.completed or calendar.event
• ✓Filter by disposition / tag
• ✓Branches: SMS, CRM update, Slack, payment link

FAQ

Frequently asked questions