customer-onboarding-call
Place a one-off welcome and onboarding call to a customer who just signed up, capture a structured result such as business type, goal, pain points, sentiment, and activation status, then write that result back to a CRM and queue a human follow-up task when the customer asks for one.
CALLE-AI · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add CALLE-AI/awesome-phone-call-agents --skill customer-onboarding-call技能说明
name: customer-onboarding-call description: Place a one-off welcome and onboarding call to a customer who just signed up, capture a structured result such as business type, goal, pain points, sentiment, and activation status, then write that result back to a CRM and queue a human follow-up task when the customer asks for one. license: MIT
Customer Onboarding Call
Use this skill when a new signup should receive a short welcome call and the business wants the conversation to end as structured data rather than as an unread recording.
customer-onboarding-call turns one signup event into at most one conversation, one structured
result, and at most one follow-up task. Obtaining that conversation may take up to three attempts on
an unreliable corridor, with only one attempt in flight at a time; see Attempts, Retries, and
Cancellation. It does not create recurring schedules, call campaigns, or contact lists. Recurrence,
if the business wants it, belongs to the host scheduler; see call-reminder.
The workflow is deliberately narrow: welcome, consent, discovery, next-step offer, wrap-up. A call that tries to sell, negotiate, collect payment, or resolve a support ticket is out of scope.
When To Use
Use this skill for:
- welcoming a customer who just signed up and confirming they can get started
- collecting first-party onboarding context: business type, goal, prior tooling, blockers
- detecting whether a customer wants a human to follow up
- turning a spoken answer into a CRM field and an assigned task
- measuring activation coverage when a team cannot call every signup manually
When Not To Use
Do not use this skill to:
- call people who did not sign up or otherwise ask to be contacted
- run sales, collections, renewal, or win-back calls
- deliver medical, legal, financial, or emergency instructions
- read pricing, delivery windows, contractual terms, or policy from memory
- retry indefinitely after a customer declines or asks not to be called
- re-call a customer who has already completed an onboarding call, unless the user explicitly asks
Required Fields
For each call, require:
customerNamephoneNumberin E.164companyNamefor the agent to introduce itself ascompanyDescription, one sentence the agent may state as fact
Optional:
businessNamelocaleandregionhints for the conversation
Ask for any missing required field. Do not infer a phone number, country code, or region from a locale, an IP address, an email domain, or unrelated prior context.
Core Workflow
- Confirm the signup is real and recent, and that this customer has not already been called.
- Build the call task from the required fields. Keep the script to roughly two minutes.
- Attach a structured result schema so the provider returns fields, not just a transcript. See
references/structured-result.md. - Persist an attempt record under a uniqueness constraint on
(signup_id, attempt_no)before dialing, and derive the provider idempotency key from it. Refuse to start a new attempt while another is in flight for the same signup. - Place the call for that attempt.
- Receive the terminal result on a webhook. Treat delivery as at-least-once and key ingestion on the provider event id.
- Classify the outcome before writing anything: Stage A decides whether a human took part, and only then does Stage B read consent. See Outcome Classification below.
- Write only what the outcome permits, then queue a follow-up task only when the outcome is
onboardedand the customer asked for one. - Schedule or cancel a retry according to Attempts, Retries, and Cancellation.
Use this shape:
signup -> attempt record -> call task + result schema -> attempt -> terminal webhook
-> classify -> permitted CRM write -> follow-up or retry or suppress
Conversation Shape
Keep the call in this order. Allow interruption at any point.
- Greet and identify. Name the customer, name the company, state that the call may be recorded if that is true in your jurisdiction.
- Ask consent. Ask whether now is a good time for a short call. If the answer is no, offer to call back later and end. Do not continue discovery after a soft refusal.
- Discovery. Ask what kind of business they run, why they signed up, what problem they want solved, and whether they have used something similar before. One question at a time.
- Offer the next step. Invite the concrete first action, and offer a human if they prefer.
- Wrap up. Summarize what will happen next, thank them, end.
The agent may answer only from companyDescription and any knowledge base you explicitly supply.
For anything else — price, delivery time, policy, availability — it must say it will have a human
follow up. Inventing these is the most common failure mode of onboarding-call agents.
State Machine
The full contract in one view. Every arrow that ends in a call is guarded; every terminal state says what it permits.
signup
|
v
[ allocate attempt no > cap? ]---- yes -->( manual handling )
| ^
no |
v |
[ attempt live (leased) ] |
| |
+-------------------+--------------------+ |
| | | |
terminal result lease expires create failed |
| | | |
| v | |
| [ reconcile with provider ] |
阅读完整来源 ↗