Hire an AI pilot customer commitment tracker

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A promise register: each accepted promise with source, owner, due date, dependency and proof needed
• A list of requests and sales statements not yet accepted
• Clashes between promises, and promises with no owner or date
• Update drafts for each customer showing only what changed
• A summary and one next step

How it does the job well

• Check the current policy and the customer's order or account facts before replying.
• Answer the actual question in the first two lines, then explain.
• Match the customer's tone. Acknowledge the problem once, without grovelling.
• Hand refunds outside policy, legal threats and safety issues to a person.

Mistakes it avoids

• Inventing facts, figures, dates, quotes or completed actions.
• Passing on an earlier step's output without checking what it says.
• Hiding a failed check to finish the run.
• Promising refunds, dates or fixes the policy does not allow.
• Copy-paste replies that ignore what the customer said.
• Closing a ticket without a clear next step.

What a good result looks like

An example, not your task: Three pilot customers each asked for a feature and nobody remembers what you agreed.

• step-01-executive-action-register.md. Register of accepted promises with source, owner, due date, dependency and proof needed.
• step-02-stakeholder-update-writer.md. Customer and team update drafts that report changes only and stay within the product's limits.
• Hand-back summary. Files saved, requests not yet accepted, gaps, checks not run and one next step.

How the work is checked

• A request or a sales statement is not an accepted delivery commitment. Completion needs actual delivery evidence.
• Use call notes only where the user says the customer agreed to share them.
• Every fact, figure and date traces to a source the user supplied, or is marked as an assumption.
• Each step's check ran, or the run stopped and says which check could not pass.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Executive action register keeper. Lists each accepted promise with source, owner, due date and proof needed, and sets aside requests not accepted. Hands step 2 the register with its status.
• Stakeholder update writer. Drafts updates showing only what changed, inside what your product can do today. Hands back drafts for each customer and for your team.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id track-promises-made-to-pilot-customers only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/track-promises-made-to-pilot-customers/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Pilot agreements or order forms, as files or pasted text
• Notes or transcripts of customer calls, only where the customer agreed to share them (optional)
• What you have delivered so far, with links or dates
• Who owns each customer
• What your product can and cannot do today

Helpful context (optional)

• Your product roadmap with dates
• Support tickets from pilot users
• Call recordings or notes, with consent
• Your pilot success criteria

Tools and access

• Any good chat AI that reads files, such as Claude, ChatGPT or Gemini: It needs agreements, notes and delivery records at once.
• Any good chat AI: It only needs your notes pasted in. A tracker connection is a bonus, not a need.

Functions and deliverables

• Pilot customer commitment tracker: Share pilot deals, call notes and delivery records. Get a list of agreed promises, owners and dates, plus customer update drafts.
  • A promise register: each accepted promise with source, owner, due date, dependency and proof needed
  • A list of requests and sales statements not yet accepted
  • Clashes between promises, and promises with no owner or date
  • Update drafts for each customer showing only what changed
  • A summary and one next step
• Action item tracker: Share meeting notes or email threads. Get action items with owners, deadlines and unresolved commitments.
  • action-register.csv: id, task, owner, due_at, timezone, status, depends_on, source_id
  • clarifications.md
  • proposed-task-changes.md
• Stakeholder update writer: Turn your rough progress notes into a weekly, monthly or launch update for leaders, engineers, partners or customers, sized to the reader.
  • A draft update sized to your reader, ready to paste
  • A status colour with a one-line reason
  • Each risk with a plan or an owner
  • Each decision with options and a recommendation
  • A list of facts you still need to add
  • A version for a second reader (optional)
  Source: Anthropic.
• Delivery update flow builder: Share shipping data and order-status contacts. Get a date rule, four updates, a tracking-page plan and a reply for late parcels.
  • Your WISMO rate and delivery accuracy, each rated against a limit
  • A delivery date rule that pads your real times
  • A four-message update flow with timing and copy
  • A tracking page plan and a script for delayed parcels
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one

Tasks you can use it for

• Three pilot customers each asked for a feature and nobody remembers what you agreed.
• You are about to send a pilot check-in and do not know what is overdue.
• Two customers were promised things that clash.
• The founder who ran the calls is leaving and handing over.

Limits to check before starting

• You want action items from internal meetings. Use the Action item tracker keeper.
• You are answering one complaint. Use the Customer reply promise checker.
• You need a go or no-go on the pilot itself. Use AI pilot decision checker.
• You have no written record of what was said. Gather notes first, as this cannot recall calls.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the workflow pack and add it to Claude, ChatGPT or Gemini.
• Paste or attach the pilot agreements, then call notes, then your delivery records.
• Say: follow the workflow file, list only accepted promises and mark missing owners and dates.
• Read the 'not yet accepted' list. Decide on each item: accept it, decline it or ask the customer.
• Check each 'done' promise has proof you can show.
• Send the updates yourself after the account owner reads them.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/track-promises-made-to-pilot-customers for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.