> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperline.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Run Hyperline on autopilot
> Use Sentinel, customer intelligence, usage tracking, notifications, exports, and AI assistants to reduce manual checks across revenue operations.
Use this guide when you want Hyperline to surface the work that needs attention instead of relying on manual checks across customers, invoices, payments, subscriptions, integrations, and usage.
Hyperline has several automation layers. They work best together: Sentinel monitors operational issues, customer intelligence monitors customer signals, notifications route findings to the right teammates, and AI assistants help investigate or execute repeatable workflows when you need more context.
## Choose the right automation layer
| Need | Use | Start here |
| ---------------------------------------------------- | ------------------------------------ | ------------------------------------------------------------------------------------ |
| Detect billing or integration issues | Sentinel | [Sentinel monitoring](../docs/sentinel/overview) |
| Monitor customer health, risk, and expansion signals | Customer intelligence | [Customer intelligence](../docs/customer-intelligence/overview) |
| Review a specific set of customers automatically | Customer monitoring agents | [Customer monitoring agent](../docs/customer-intelligence/customer-monitoring-agent) |
| Route customer updates to the right people | Owners, followers, and notifications | [Owner and followers](../docs/customer-intelligence/owner-followers) |
| Track adoption, consumption, and product milestones | Custom usage tracking | [Custom usage tracking](../docs/customer-intelligence/custom-usage-tracking) |
| Prioritize collections follow-up | Late payment behavior | [Late payment behavior](../docs/customer-intelligence/late-payment-behavior) |
| Answer questions or run assisted workflows | Hyperline AI tools | [AI assistant setup](./ai) |
## What each layer does
Watches billing operations and creates tasks for issues such as failed payments, late invoices, disconnected integrations, and subscription errors.
Reviews customer context across usage, billing, payments, ownership, support, and communication signals.
Shows custom usage metrics on customer records so teams can monitor adoption, consumption, and plan limits.
Connects Hyperline to AI assistants through MCP, the CLI, and reusable workflow skills.
## Recommended setup
### 1. Start with Sentinel
Use [Sentinel monitoring](../docs/sentinel/overview) for operational issues that should not depend on someone checking lists manually.
Sentinel is useful for:
* Failed or late payments
* Draft or overdue invoices
* Disconnected payment providers or integrations
* Subscription renewal issues
* Electronic invoicing failures
Give the right teammates access to Sentinel tasks so operational issues reach the people who can resolve them.
### 2. Add customer intelligence
Use [customer intelligence](../docs/customer-intelligence/overview) when you want to prioritize accounts based on customer context, not only billing exceptions.
Customer intelligence can help you monitor:
* Customers with payment risk or late payment patterns
* Accounts with declining or growing usage
* Strategic customers approaching renewal
* Expansion opportunities based on adoption or consumption
* Customers with weak communication or unresolved support signals
Create a [customer monitoring agent](../docs/customer-intelligence/customer-monitoring-agent) from **Customers > Monitoring**. Start with **Autopilot** when you want Hyperline to choose the schedule and signal weighting, or use **Advanced** mode when you want to focus the agent on a specific segment or workflow.
### 3. Route findings to owners and followers
Assign [owners and followers](../docs/customer-intelligence/owner-followers) so customer findings have a clear audience.
Use this when:
* Account owners should receive customer health findings
* Finance teammates should follow payment-risk segments
* Customer success managers should follow strategic accounts
* Managers need visibility without becoming the customer owner
Each user can also manage notification channels from **Profile > Notifications**.
### 4. Expose usage signals
Use [custom usage tracking](../docs/customer-intelligence/custom-usage-tracking) to display product-specific metrics on customer records.
Good usage metrics include:
* Seats used
* API calls
* Storage consumed
* AI credits spent
* Active workspaces
* Feature adoption milestones
These signals help teams spot adoption risk, upsell readiness, and customers approaching plan limits.
### 5. Connect AI assistants for deeper workflows
Use [Hyperline AI tools](./ai) when an assistant needs to investigate, explain, or prepare repeatable revenue workflows.
For example, an assistant can help:
* Investigate a customer balance
* Build an insights report
* Answer a billing question
* Draft a quote or invoice workflow
* Plan a bulk subscription update
Use [Hyperline MCP](../api-reference/docs/ai/mcp) when your assistant supports MCP, or [Hyperline CLI](../api-reference/docs/ai/cli) for terminal-based assistants and scripts.
## Example workflows
| Workflow | Hyperline setup |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| A payment provider disconnects | Sentinel creates a task and links to the affected integration. |
| A strategic customer has declining usage before renewal | A monitoring agent reviews the customer, combines usage and account context, and can notify the owner. |
| A finance team wants to prioritize collections | Create a late payment behavior segment, follow the segment, and use Sentinel for invoice-level payment issues. |
| A customer is approaching an AI credit limit | Display the credit or usage metric on the customer record and use customer intelligence to surface expansion context. |
| A manager wants a weekly revenue review | Use analytics, exports, and AI assistant workflows to summarize subscriptions, invoices, payments, usage, and customer signals. |
## Next steps
* Configure [Sentinel monitoring](../docs/sentinel/overview) for operational issue detection.
* Create a [customer monitoring agent](../docs/customer-intelligence/customer-monitoring-agent) for strategic customer segments.
* Set up [owners and followers](../docs/customer-intelligence/owner-followers) so findings reach the right teammates.
* Connect [AI assistants](./ai) for assisted investigation and repeatable workflows.