Framework
Seven personas
Agent Relations is shared work. These are the seven roles that carry it, what each is responsible for, which domains each leads and the questions each asks.
Executives
Set the ambition, fund the work and decide how far the organization lets agents act for and with it.
- Responsibilities
- Decide how much the organization lets agents do for and with it, and where it draws the line.
- Fund the practice and name an accountable owner for each domain.
- Review progress against the Maturity Model and the Measure KPIs.
- Leads
- No domain alone. Sponsors all of them and contributes to the ones that carry risk.
- Questions it asks
- What do agents say about us today, and is it right?
- Which of our competitors do agents recommend instead of us?
- What would we let an agent do for a customer without a person in the loop?
Marketing and brand
Own the story agents tell: accurate facts, positioning, reputation and presence where agents look.
- Responsibilities
- Own the facts and the story that agents repeat: positioning, claims, reputation.
- Keep presence consistent across the site, directories, listings and review sources agents read.
- Test what agents say about the organization and correct what they get wrong.
- Questions it asks
- If someone asks an assistant who we are, what do they hear?
- Which sources do agents quote about us, and do we control them?
- Are our claims precise enough to survive being repeated word for word?
Engineering and product
Build the access, data, endpoints and actions that agents use, on open standards.
- Responsibilities
- Publish structured data, feeds and documentation in open standards.
- Build and run the endpoints and actions agents call, with sensible limits.
- Implement identity, authorization and logging for agent traffic.
- Questions it asks
- Which agents reach us, and which are we blocking by accident?
- Which of our workflows can be exposed as an action with clear inputs and results?
- How do we tell a verified agent from one that only claims a name?
Commerce and sales
Make offers, prices, availability and checkout work for agents buying on someone’s behalf.
- Responsibilities
- Keep offers, prices, availability and delivery terms accurate and machine-readable.
- Make checkout and quoting work for an agent buying on someone’s behalf.
- Decide which agent-led sales channels and protocols to support.
- Leads
- Transact
- Questions it asks
- Can an agent see real stock and the real price, right now?
- What happens when an agent buys, returns or disputes an order?
- Which agent-referred sales are we winning, and which are we losing?
Service and operations
Answer agents’ questions, hand off to people well and keep promises made through agents.
- Responsibilities
- Answer the questions agents ask, quickly and in the same way a good person would.
- Hand off to a person when an answer needs judgment, and say so to the agent.
- Honor what was promised through an agent, and review failures.
- Leads
- Converse
- Questions it asks
- Which questions do agents ask us most, and do we answer them well?
- When an agent cannot be answered, where does the request go?
- What did we promise through an agent that we could not keep?
Legal, risk and security
Set the policies: which agents may do what, identity, data, disclosure and liability.
- Responsibilities
- Write the policy: which agents may do what, with what data and under what terms.
- Set identity, permission and disclosure rules, and decide who is liable for what.
- Review agent access, logs and incidents.
- Leads
- Trust
- Questions it asks
- Who is this agent acting for, and can we verify it?
- What may an agent commit us to, and up to what value?
- What do we owe the person behind an agent in disclosure and consent?
Agent Relations practitioners
The central team or lead that runs the practice, sets standards inside the organization and enables everyone else.
- Responsibilities
- Run the practice: assess, plan, report and keep the Framework current inside the organization.
- Define internal standards, KPIs and reporting, and keep them consistent.
- Enable every other team with templates, training and review.
- Leads
- Measure
- Questions it asks
- Where are we on the Maturity Model, domain by domain?
- Which single improvement would move the most outcomes next quarter?
- Which team needs help, and what is it blocked on?
Responsibility matrix
Who does what in each domain. Leads owns the outcome and makes the call. Contributes does part of the work or must be consulted. Informed needs to know the result.
| Persona | Discover | Describe | Converse | Transact | Trust | Measure |
|---|---|---|---|---|---|---|
| Executives | Informed | Informed | Contributes | Contributes | Contributes | Contributes |
| Marketing and brand | Leads | Leads | Contributes | Informed | Contributes | Contributes |
| Engineering and product | Contributes | Leads | Leads | Leads | Contributes | Contributes |
| Commerce and sales | Contributes | Contributes | Informed | Leads | Informed | Contributes |
| Service and operations | Informed | Contributes | Leads | Contributes | Contributes | Contributes |
| Legal, risk and security | Informed | Contributes | Contributes | Contributes | Leads | Informed |
| Agent Relations practitioners | Contributes | Contributes | Contributes | Contributes | Contributes | Leads |
Several personas can lead one domain. In that case they agree a single named owner inside the organization. The matrix is a starting point for how an organization assigns work, not a rule about job titles.