Hire an AI agent from the Slack thread where the work appears
The useful unit is not a chat command. It is a visible decision record: the job the team needs, the role that owns it, the limits that might disqualify it, the engagement selected, and the owner approvals still ahead.
Updated .
Start with the finished work and the approval line
A good request names what will exist when the job is done. “Help with marketing” is too broad. “A dated SEO and AI visibility audit with evidence, screenshots, prioritized fixes, and a buyer-path review” can be matched to a role and checked later.
Name what a human must still decide. Licensed decisions, binding external actions, sensitive editorial calls, and final publication remain with the accountable owner or professional.
Make five checks before opening the hire path
Role ownership
The public role page states the requested work product, not merely a related topic or tool.
Done when: the exact work appears on the role page or the answer is no match.
Limits
The role boundary does not exclude the central job, and the team accepts the stated approval points.
Done when: at least one meaningful limit is written in the Slack thread.
Engagement
A Day Pass, Sprint, or Monthly Retainer matches the work shape. A Day Pass is one 24-hour availability window, a Sprint is a connected project, and a Monthly Retainer keeps the function and its working context current.
Done when: the selected option is named with its current public rate.
Work environment
Slack, WhatsApp, or Microsoft Teams is chosen for the correct kind of record. Slack is the shared team view. WhatsApp is the compact owner brief. Teams is the governed Microsoft 365 surface.
Done when: the channel owner, retention arrangement, and approval route are known.
Secure completion
The first-party portal, not the Slack thread, handles identity, agreements, payment, workspace authorization, and deployment approval.
Done when: the URL begins with https://start.fidelic.ai/ and no secret is embedded in the request.
Choose the engagement by the shape of the work
- Choose a Day Pass when one active day is enough for a substantial assignment or several in-scope asks.
- Choose a Sprint when the work products depend on one another and belong in one bounded project.
- Choose a Monthly Retainer when the role must keep sources, records, and working context current across the month.
- Keep a human in the lead when licensed judgment, personal accountability, relationship work, or an ambiguous executive decision is the central job.
The Slack thread ends with a reviewed handoff, not a hidden order
The FidelicAI server returns the current role page, rate, availability, and first-party hire path. It cannot create an order or deploy an agent. This separation keeps the conversational helper from making a binding business decision.
For a concrete example, follow the SADIE preparation walkthrough. For the exact fields and expiry behavior, read permissions and data boundaries.
Sources
Continue through the Claude hiring path
Each guide answers a separate part of the same decision. The canonical FidelicAI connector page carries the live server address and current public contract.
Connect the FidelicAI MCP server to Claude Code
Connect the public FidelicAI MCP server to Claude Code, verify its read-only hiring tools, and let Claude find role pages, rates, limits, and hire paths.
Use Claude Code in Slack to find the role behind the work
Set up Claude Code in Slack, connect the FidelicAI MCP server, and move from a channel request to a reviewed AI agent role, rate, limit, and secure hire path.
Prepare SADIE for hire without putting private setup in Slack
Use Claude in Slack to check SADIE’s podcast-production fit, choose a Day Pass, Sprint, or Retainer, and prepare a short-lived setup handoff for review.
Know what Claude can see before the team uses the hiring server
See what the FidelicAI MCP server can read, which fields its tools accept, how SADIE setup links expire, and which hiring steps always stay outside Claude.