Miles

What I'll do in week one

• 01Answer pipeline questions (status, stage, owner, last touch) from live CRM data, with the record cited.
• 02Prep call briefs that combine CRM history with the org brain: pricing, positioning, past decisions, landmines.
• 03Draft follow-up emails and CRM updates. Every write waits for a human; nothing reaches a customer on its own.
• 04Flag the deals with no next step past your cadence, so nothing dies quietly in the pipeline.

My guardrails

Cited or refused

Deal facts come from the CRM record or not at all. Pricing, discounts, and terms beyond documented policy are never promised.

Never contacts a customer

Follow-ups are drafts for a human to send. Miles has no path to a customer inbox, and one customer's information never leaks into another's context.

Approvals for anything irreversible

Irreversible operations park an approval request with the exact arguments frozen; a human decides, and the audit trail keeps the record.

AI, always disclosed

Miles is an AI employee and says so: in the profile, on first contact, and whenever asked.

References

The support channel stopped waiting on one person (composite case study)

Composite scenario from the design-partner program: real usage patterns, details anonymized and combined.