AI Workforce

Specialists for the work your business does every day.

Give each AI specialist a defined role, a clear assignment, and only the access it needs. Your team sets the boundaries. Ciright coordinates the work. These twelve roles are a proposed catalog. They are not twelve agents included in the standard seat.

Effective access cannot exceed the intersection of the user or delegation, the agent, the organization, the application, the object, and the action. That rule has to be enforced on the server. A hidden button or a prompt is not authorization. Retrieved content is untrusted data, not a new instruction.

A failed run is not a success. A sent message is not necessarily delivered, opened, or read. An inferred intent is not a known fact. This marketing site does not execute tools or open private records.

Executive coordination

Prepare the daily brief and surface decisions.

Purpose: Help a person start from the work that needs attention.
Inputs: Authorized calendar, task, and activity records.
Tools: My Day, MyCalendar, and Works, and only the records that person may use.
Permitted output: A brief and a list of decisions. Not an unsupervised change to those records.
Example assignment: Prepare tomorrow's customer meetings and flag decisions that need a person.
Owner: An accountable person in the World. This site does not assign a named production owner.
Approval boundary: Follows the action's risk and the organization's policy.
Source evidence: My Day, MyCalendar, and Works are named in this repository. A live agent identity is not.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

Scouting

Research companies and relevant stakeholders.

Purpose: Gather permitted source material with evidence links.
Inputs: Sources the organization has allowed, plus evidence the person can open.
Tools: Scouting, if that product is later confirmed. This repository does not contain it.
Permitted output: Research notes with links. Not a claim that a company is a Ciright customer.
Example assignment: Summarize public information about a prospect and list the sources.
Owner: Unassigned until a product owner is confirmed.
Approval boundary: Using a new source, or stating a fact externally, needs the applicable policy.
Source evidence: No Scouting route or registry record is in this repository.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

Hunting

Develop prospect lists and proposed outreach.

Purpose: Prepare sales development work the person can review.
Inputs: Existing sales records the person may use.
Tools: Existing sales tools. Outreach still needs authorization and consent.
Permitted output: A proposed list and draft outreach. Sending is a separate, permitted action.
Example assignment: Draft a prospect list and the first note, and leave the send for approval.
Owner: Unassigned until the sales tool owner is confirmed.
Approval boundary: Outreach is not sent from the draft. Consent and authorization stay with the organization.
Source evidence: Pipeline and CRM are named. A live hunting agent is not.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

Fishing

Explain observed engagement and intent.

Purpose: Describe signals the products actually recorded.
Inputs: Fishing and Analytics records the person may see.
Tools: Fishing and Analytics. No invented identity or engagement.
Permitted output: An explanation of observed events. An inference is labeled as an inference.
Example assignment: Explain which sample pages were visited, without claiming why the visitor will buy.
Owner: Unassigned. Fishing has no route in this repository.
Approval boundary: Acting on an inference, such as contacting someone, is a further action.
Source evidence: Fishing and Analytics are named in the application map. Live data access is not verified.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

LISA — sales coordination

Prepare sales actions and keep follow-up organized.

Purpose: Coordinate sales work once the existing LISA contract is confirmed.
Inputs: CRM and Pipeline records the person may use.
Tools: Confirm the existing LISA contract, CRM, and Pipeline mapping before any live use.
Permitted output: Prepared sales actions and an organized follow-up list.
Example assignment: List follow-ups that are due and draft the next step for approval.
Owner: Not confirmed. No LISA contract is in this repository.
Approval boundary: CRM and pipeline writes follow the owning application's policy.
Source evidence: No LISA product, contract, or field mapping was found in this repository.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

Marketing

Draft campaign plans and supporting content.

Purpose: Prepare marketing work for a person to approve before publication.
Inputs: Existing content and campaign records the person may use.
Tools: Existing content and communication tools. Publication is a separate approval.
Permitted output: Draft plans and draft content. Not a published campaign.
Example assignment: Draft a launch outline and the pages it would need.
Owner: Unassigned until the content tool owner is confirmed.
Approval boundary: Publication waits for the organization's approval policy.
Source evidence: No campaign product is verified in this repository. Broadcast is named and has no route.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

Customer success

Surface commitments, support issues, and renewal tasks.

Purpose: Keep customer commitments visible to the people who own them.
Inputs: Verified customer-service and CRM records.
Tools: Those records only. A support tool is not named in the application map.
Permitted output: A list of commitments and suggested tasks. Not a closed support case unless the owning tool records one.
Example assignment: List renewal tasks and open commitments for a sample account.
Owner: Unassigned. No customer-service system of record is verified here.
Approval boundary: Customer communications and case changes follow the owning tool.
Source evidence: CRM is named. A support system was not found.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

Operations

Coordinate projects, tasks, handoffs, and exceptions.

Purpose: Keep operational work moving across the applications that own it.
Inputs: Works records and the business applications that own the related objects.
Tools: Works and those owning applications.
Permitted output: Coordinated tasks and exception notes.
Example assignment: Show which handoffs are late and who owns the next step.
Owner: Unassigned as a live agent. Works is named in the repository.
Approval boundary: Changing ownership or dates follows Works and the organization's policy.
Source evidence: Works is in the application map and has a workspace screen. A live operations agent is not verified.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

Finance

Prepare summaries and flag financial exceptions.

Purpose: Help a person review figures the finance system already holds.
Inputs: Approved finance connectors. None are verified in this repository.
Tools: Those connectors only. No autonomous payment authority.
Permitted output: Summaries and exception flags. Not a payment, refund, or ledger posting.
Example assignment: Flag sample invoices that do not match the purchase record, without paying them.
Owner: Unassigned. No finance connector is in the repository.
Approval boundary: Any movement of money remains a human-authorized action in the owning system.
Source evidence: The workspace has a billing screen. It is not a verified finance connector or payment authority.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

People and HR

Coordinate onboarding and administrative workflows.

Purpose: Prepare people-process steps for the humans who make employment decisions.
Inputs: HRM records, restricted to the people allowed to see them.
Tools: HRM, which is not in this repository's application map.
Permitted output: Checklists and draft administrative steps. Not a hiring, firing, or compensation decision.
Example assignment: Prepare an onboarding checklist for a new teammate.
Owner: Unassigned. HRM was not found in this repository.
Approval boundary: Employment decisions stay with people. Personnel data stays restricted.
Source evidence: Teams is the people-related product in the map. HRM is not.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

Procurement

Compare authorized supplier information and prepare requests.

Purpose: Prepare purchasing work inside the spending policy.
Inputs: Verified purchasing tools and supplier records.
Tools: Those tools only. None are named in this repository.
Permitted output: Comparisons and draft requests. Not a purchase.
Example assignment: Compare two approved suppliers and draft the request for a person to submit.
Owner: Unassigned.
Approval boundary: Spending follows the organization's approval policy.
Source evidence: No purchasing product is in the application map.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.

IT and governance

Explain access, tools, and agent activity.

Purpose: Help administrators understand what is allowed and what an agent did.
Inputs: Connect, Keyra, and existing history the administrator may see.
Tools: Connect, Keyra, and On The Line. No self-granted privileges.
Permitted output: Explanations of access and activity. Not a permission change unless an administrator makes one in Connect.
Example assignment: Explain which applications a sample agent can read, and where that grant would be revoked.
Owner: An administrator, once a live agent exists. None is verified here.
Approval boundary: Permission changes stay in Connect and with Keyra where step-up applies.
Source evidence: Connect, Keyra sign-in, and On The Line are implemented or named in this repository. Agent enforcement on a live registry is not verified.
Status: Proposed
Availability: Proposed role. Not verified as a live agent, and not included as one of twelve agents in the $4.99 seat.
Plan and usage: Plan eligibility and usage charges are not in an approved public catalog.