Plan@Job has three distinct ways to work with AI: named staff carrying out configured background workflows, Ask Plan@Job for conversations you start, and an MCP connection for a compatible external AI client. Choosing between them starts with the task you want to complete.
Use AI staff for recurring administration
Sophie Bennett supports clarification on existing job briefs. Daniel Reed helps with eligible subcontractor coordination and follow-ups. Maya Collins prepares deposit and overdue-payment actions for review.
These roles work within configured account settings. You choose supervision, review activity and make the decisions that require approval. Their work depends on job prerequisites and operating limits. The staff do not promise to carry out every task mentioned in a free-text instruction.
The AI team guide explains each role, including what it cannot decide.
Use Ask Plan@Job when you want to inspect or act
The in-app assistant is a conversation you initiate. Its supported tools can help inspect job and network information and request available actions. The account's role and permissions determine what is accessible.
A useful request names the context and the result you need, such as finding the job you want to review or inspecting the subcontractor assignments on it. Read the result and review any proposed action before assuming the business state has changed.
A chat response, a proposed action and a completed action are different things. That distinction matters most for messages, quote decisions and other commitments.
Use MCP to connect a compatible external AI client
MCP provides a connection through which a supported external AI client can access the capabilities granted to it. This is separate from hiring Plan@Job's hosted staff. Connecting a customer's own AI subscription does not transfer that subscription's usage to the background staff system.
Setup and availability depend on the client, account and device. The current MCP installation guide explains the supported setup routes and the checks to perform. It distinguishes protocol support from a completed connection in a particular provider account.
Choose by the working pattern
- For repeated eligible job follow-ups, start with the appropriate AI staff role.
- For a question or action you want to initiate inside the product, use Ask Plan@Job.
- For supported access from an external AI application, use the connection guide and verify the account permissions.
These options can complement each other. They should not be treated as interchangeable promises of unrestricted automation.
Keep authority clear
Account permissions, supervision and action-specific approval rules remain relevant whichever interface you use. Writing “do everything automatically” does not create permissions the account lacks or remove approval conditions attached to commercial decisions.
Start with a read or a low-impact inspection, confirm that the information belongs to the correct account and understand what the next action will do. Use the product's records to verify completion rather than relying solely on conversational wording.
Common questions
Do I need to connect an external AI before hiring staff?
Hosted staff run within Plan@Job. MCP is a separate connection option.
Will connecting my AI change what search engines say about Plan@Job?
No. An account integration and public product discovery are separate. Public pages and documentation explain the product to readers and search services.
Where are the connection steps?
Open Connect your AI, then follow the current guide for your supported client and account.