Capabilities
Permission
May this teammate do it?
Grant only the tools, business areas, memory, research, and channels the role needs.
AI Teammates
Give the work a responsible owner.
A Loquent teammate is not a chat window with a new name. It is a durable role with goals, instructions, business context, memory, permissioned tools, and a clear way to ask for judgment.
Every new teammate begins in Suggest mode
Role brief
Maya · Front desk
Warm, concise voice
Book qualified requests
Never invent availability
Ask on exceptions
The role stays consistent across the customer entrances assigned to it.
The anatomy
Human-shaped work. Machine-scaled follow-through.
Loquent borrows the useful structure of a dependable colleague: a role, a way of working, context, memory, authority, and accountability. It never needs to pretend the teammate is human.
01
Identity
A role with a job to own
Persona and goals give the teammate a consistent way to show up and a result to pursue.
02
Method
Skills and business knowledge
Playbooks teach how to work; reference material supplies the facts it should use.
03
Continuity
Memory and learned judgment
Durable facts and repeated review signals help future work start sharper.
04
Authority
Capabilities, rules, and autonomy
Permissions define what is possible. Rules define the boundary. Autonomy defines what needs review.
What every teammate carries
Seven parts. One coherent role.
Each part solves a different trust problem. Follow the deeper pages to see exactly how the controls fit together.
Who it is at work
Role, persona, and goals
The job it owns, the character it presents, and the business outcome it keeps moving toward.
Explore this layerWhere judgment stops
Rules and escalation
Non-negotiable boundaries plus a plain-language path back to the Leader when the answer is not routine.
Explore this layerHow it does the job
Skills
Reusable playbooks and instructions that teach a teammate how to handle a kind of work.
Explore this layerWhat it may touch
Capabilities
Permissioned tools, business data, memory, research, and communication channels granted for the role.
Explore this layerWhat the business says is true
Knowledge
Focused reference material such as pricing, policies, hours, and frequently asked questions.
Explore this layerWhat carries forward
Memory and learning
Durable facts and review-driven lessons, with approval, undo, rollback, and pinned boundaries.
Explore this layerProduct evidence
Build a roster around the jobs that recur.
A front-desk teammate should not need the same goals or authority as a sales teammate. Loquent keeps each role distinct while they share the organization’s context and customer record.
Schedules
Standing work, described in a sentence.
A morning briefing, a Friday follow-up sweep, a monthly recap of leads that went quiet. Describe the routine in plain language and your teammate runs it on its own — you see what fires next, when it last ran and how it went, and can run it now.
Trust is designed
Three questions keep authority legible.
The system separates what a teammate can access, when it may act, and which decisions must return to a person.
Autonomy
Review posture
May it proceed without approval?
Suggest is the safe starting point. Autonomous is an explicit, reversible choice.
Escalation
Human judgment
Does this decision belong to you?
When the teammate reaches a real exception, it pauses and asks instead of inventing certainty.
Keep exploring
See how the rest of the system connects.
Start with the role you wish had an owner.
Request an invitation and describe the recurring customer-facing job. We’ll help shape the teammate, its context, its permissions, and the decisions it should always bring back.
No teammate begins with autonomous sending enabled.