Using Orbit
Orbit is a staff tool inside your Seedly CRM. It can read authorized CRM data, build inline tables/charts, and propose actions you review before execution. It uses your connected AI provider and your installation's CRM API.
A normal conversation
Choose the right subaccount, start a conversation, and ask one concrete question. Specify date range, timezone and whether you need a sample or a complete report. Review source disclosures and pagination limits before treating a chart as an account total. Continue in the same conversation when following up; start a new one for a different task.
An AI reply is not evidence that a write completed. Orbit creates a review card with the actual operation, account and fields. Approve or dismiss it. Approval expires after 15 minutes and execution rechecks permissions. After a timeout or unknown result, inspect the native CRM before proposing the action again. API acceptance of an email or campaign is not delivery confirmation.
Workspace and floating chat
The full workspace puts Chat, Code changes, Agents and Inbox above your conversation history. Support, Saved prompts, Capabilities and Settings sit below it. The floating popup has one header: history, new conversation, expand and close. Open history to reach secondary tools; expand for account switching and conversation management. Rename, pin and archive are in the full workspace toolbar. Rename edits the title in place. Archive is reversible; conversations are private to their creator. On small screens, history opens as a drawer; select a conversation or press Escape to return to your work.
Move the closed launcher by dragging or with arrow keys. Escape closes the popup. Settings offers the standard bubble, pixel companions, a custom PNG/JPEG/WebP upload or Hidden. Uploads remain on that browser for that user/location; they do not go to the AI. The agency's Floating chat switch takes precedence.
The message box grows as you type. Enter sends; Shift + Enter adds a new line. You can copy a message from its header. Reading earlier messages keeps your place when a reply arrives; Back to latest returns to the newest reply.
When Local Codex is connected, the selector in the message box switches between code help and the CRM assistant. The choice is remembered for that conversation during the browser session. CRM starter prompts choose the CRM assistant. Voice and screen controls open from Voice when enabled for the selected assistant.
An administrator can open a code request directly from chat. The review occupies the conversation area so there is space for source selection and the complete diff. Back to chat restores your draft and reading position. Existing requests keep their setup collapsed while you review; expand New code request to prepare another proposal. Creating a draft PR still requires the explicit review checkboxes.
Account settings
Agency owners/admins with settings permission configure location enablement, agency access, floating chat, reviewed writes, provider/model, daily turn allowance and approved extension routes. A staff user's native CRM permissions still apply even if the backend API key has broader scopes. Account-wide resource access is currently required; own/team scopes are refused.
Connect OpenRouter, select a tool-capable model and Save settings. The daily allowance counts turns, not dollars. Use provider-side spending limits. Key verification checks the credential without making an inference request; a real reply is needed to confirm credits and model access.
Appearance can follow the account's brand tokens, use Clear light or Clear dark, or set custom background/accent colors. Changes apply to the workspace and popup for that subaccount. Launcher choice and position are personal browser preferences.
Data and limits
Selected CRM results and bounded conversation history are sent to the chosen provider. Keys stay server-side and saved OpenRouter keys are encrypted per location. Do not put credentials in a chat or a tool description. Retrieved CRM text is data, not authorization to run instructions contained in a note or message.
Orbit does not provide arbitrary database, shell, URL or browser execution. The installed catalog defines supported operations. A CRM screen does not prove there is an API for it. Generic extension calls are manager-only, require an exact allowlist and live granted discovery. New integrations need implementation and testing.
Replies appear when a bounded run completes; token streaming is not implemented. Search covers loaded conversation titles; load older chats to include more. Charts describe retrieved data unless a verified reporting endpoint returns complete aggregates. Provider/tool availability and charges depend on your configured account. See Validation for the evidence and limits of this release.
Guided agents (0.2.0-alpha.1)
See Guided agents for setup, rehearsals, schedules, review, limits and upgrade verification. Deploy the new backend before the frontend. Existing conversations remain available; the upgrade adds two private tables and does not enable any scheduled job automatically.