Fulcrum Docs Guides

Fulcrum Cortex and Sessions: directing your AI team

Understand Cortex, the AI execution layer, and Sessions, the orchestrator; give Sidekicks clear tasks, review permissions and verify completed work.

Fulcrum Cortex is the AI execution layer for business. Fulcrum Sessions is the orchestrator: humans and AI as one team. Code builds and runs software, Lyre handles voice, and CRM holds the customer relationship. Sidekicks are AI teammates working with the tools and access you connect.

Give an outcome, context and limits

Prepare a follow-up for the demo enquiry.
Read the relevant customer record and last conversation.
Draft the reply and suggest two available meeting times.
Show me the draft and the source record before sending anything.

A useful task names the result, the source of truth and the actions that need approval. Tell the assistant what “done” means: draft ready, message sent, record updated or release verified live are different endpoints.

Use connected channels

Cortex is designed to work through Discord, Telegram, WhatsApp and Slack. Availability depends on your configured channel and workspace. Use the conversation assigned to the intended assistant and project; a different thread can have different context and access. See Cortex channels for the platform overview.

Connect tools deliberately

Check the signed-in account, workspace and permissions when connecting an app. An agent may be able to read but not edit a record. A skill describes a method; it does not create missing credentials or permission. Reconnect or adjust the intended scoped access if an action is unavailable.

Follow progress and verify

  1. Ask for a short plan and milestones for work spanning several products.
  2. Review approval requests against the original task.
  3. Ask for evidence of the result: a document, a record link, a sent item or the live revision.
  4. Check outstanding failures and skipped actions before accepting completion.

Common cross-product workflows

  • Lyre answers an enquiry, with results reviewed in CRM.
  • Calendar booking pages let customers choose a time; Meetings hosts the conversation.
  • Code builds a change, with checks and publication included when requested.
  • Docs and Drive keep plans and shared material accessible to the right people.

If the assistant cannot act

Check the selected assistant, connection, workspace, permission and account allowance. Ask it to distinguish a failed attempt from a confirmed blocker and to report the concrete next action. Do not send passwords or tokens in a channel to resolve a connection error.

Last updated