01
Customer owns the source account, app, bot, mailbox, or workspace.
Guided Configuration
Setup Guides
After ordering, connect the systems your AI Team needs. Each setup stays scoped, approval-gated, and evidence-ready.
Connection Scope
Three Setup Paths
Universal Rule
Configuration is narrow by default.
02
LaneFrame receives only the minimum permissions approved for the selected AI Team instance.
03
Every integration is mapped to a workflow owner, approval gate, evidence plan, and escalation route.
04
Sensitive actions remain approval-gated unless the customer explicitly enables low-risk execution.
Integration Tutorials
Connect the tools your team already uses.
Guide 01
Slack
Team communicationRoute approvals, status updates, escalations, and evidence summaries into governed channels.
Real product interface
See the reviewable execution evidence.
Test workspace · identifiers redacted · product capability evidence, not a customer result or ROI claim.
Captured product screenshotTrace & Evidence
Request-to-result flow
A captured product evidence flow showing how a request becomes a reviewable operating output.
- Claim supported
- Request, result, evidence, and review context are rendered by real product components.
- Does not prove
- Customer deployment success or live connector state.
- Source
- test-workspace · Fixture/test labels; no customer identifiers
- Provenance
- Captured product route recorded
Prepare
- Slack workspace admin access
- Approved channels for AI Staff work
- Escalation owner list
- Message approval rules
Allowed Permissions
- Read approved channel context
- Post status updates
- Create approval requests
- Escalate to named owners
Guided Setup Steps
- Create or approve a LaneFrame AI Staff app connection for the workspace.
- Grant only the channel, message, and user lookup permissions approved for the selected AI Team instance.
- Invite the AI Staff app to the approved operating channels.
- Map each channel to a workflow, owner, approval gate, and escalation rule.
- Send a test approval request and confirm the evidence log records channel, actor, timestamp, and result.
Done whenAI Staff can post and receive governed workflow updates in approved Slack channels only.
Guide 02
Telegram
Lightweight command and alert channelSend concise alerts, owner approvals, and workflow status messages to approved chats.
Prepare
- Telegram bot token or approved bot owner
- Approved chat or group IDs
- Escalation recipients
- Allowed command list
Allowed Permissions
- Send alerts
- Receive command responses
- Record approval replies
- Escalate unresolved work
Guided Setup Steps
- Create a Telegram bot with the customer-controlled bot owner account.
- Add the bot to the approved group or direct operating chat.
- Register the chat ID and allowed commands inside the guided configuration.
- Restrict AI Staff behavior to approved alerts, approvals, and status messages.
- Run a test alert, approval response, and escalation handoff before production use.
Done whenAI Staff can use Telegram for controlled alerts and approvals without broad chat access.
Guide 03
Monitor approved mailboxes, draft responses, classify requests, and create evidence-backed follow-ups.
Prepare
- Shared mailbox or OAuth admin approval
- Allowed labels or folders
- Outbound approval policy
- Sender identity rules
Allowed Permissions
- Read scoped mailbox items
- Apply labels
- Draft replies
- Send only approved message classes
Guided Setup Steps
- Choose the mailbox scope: shared inbox, support inbox, billing inbox, or sales inbox.
- Connect through OAuth or a restricted mailbox credential controlled by the customer.
- Limit AI Staff to approved folders, labels, senders, and workflow categories.
- Set which emails are draft-only, approval-required, or allowed for low-risk sending.
- Run test cases for classification, draft response, approval, send, and audit evidence review.
Done whenAI Staff can operate inside the selected mailbox scope with clear send and approval boundaries.
Integration permission preview
Supported channels do not become unrestricted access.
Slack
- Allowed action
- Post reviewable Staff cards
- Boundary
- Approval required for external actions
- Evidence
- Request, Staff, outcome, and trace remain reviewable.
Telegram
- Allowed action
- Receive controlled requests
- Boundary
- Workspace boundary applies
- Evidence
- Request, Staff, outcome, and trace remain reviewable.
- Allowed action
- Route lead operations context
- Boundary
- Trace evidence retained
- Evidence
- Request, Staff, outcome, and trace remain reviewable.
Evaluation notes
Self-serve trial first. Internal review materials stay clear.
Security review
Use Governance, Security, and the Security Overview to review current controls and evaluation boundaries.
Legal review
Review Terms, Privacy, Cookies, and any separately signed agreement before internal approval.
Internal approval
Use Trial terms, Pricing, and Cost Comparison to explain package scope.
Invoice payment
Handle non-card purchasing through a separate approved process if needed.
Order Path