ServiceFlow Pro Docs
AI & Automation

AI Entity Insights

Elijah Johnson · Published · Updated · 5 min read
AI Entity Insights is a short list of bullets on a customer, job, or invoice. AI Entity Insights surfaces short, actionable bullets on customer, job, and invoice records, recurring-customer signals, follow-up timing, pricing notes, and checklist hints. Open a customer, a job, or an invoice.
Open any supported record: - Customers to customer detail - Jobs to job detail. Invoices to invoice detail Look for the AI Insights card on the page layout. View insight list with title, body, and severity tags (info/warning/success). Refresh insights on demand (when refresh control is shown). See AI vs Quick tips badge based on OpenAI configuration. Link to Settings to Integrations to OpenAI when not configured. OpenAI Setup Guide completed for full AI insights. Permission to view the underlying entity (customer/job/invoice). Sufficient record data (history, totals, status) for meaningful suggestions. Settings to Integrations to OpenAI to enable and test API key. Open Jobs to select a job. Click Refresh after updating job notes or status for new suggestions. Config-gated, without OpenAI, card may show placeholder text or generic tips only. Insights are advisory, not automatic workflow changes. /docs/guides/ai-integration-guide step 3 is Enable insights (admin).

Overview

AI Entity Insights surfaces short, actionable bullets on customer, job, and invoice records—recurring-customer signals, follow-up timing, pricing notes, and checklist hints. With OpenAI enabled, insights are AI-generated; otherwise quick static tips may appear.

How to access

Open any supported record:
  • Customers → customer detail
  • Jobs → job detail
  • Invoices → invoice detail
Look for the AI Insights card on the page layout.

How do you view insight list with title, body, and severity tags (info/warning/success)?

View insight list with title, body, and severity tags (info/warning/success).
  • View insight list with title, body, and severity tags (info/warning/success).
  • Refresh insights on demand (when refresh control is shown).
  • See AI vs Quick tips badge based on OpenAI configuration.
  • Link to Settings → Integrations → OpenAI when not configured.

Prerequisites

  • OpenAI Setup Guide completed for full AI insights.
  • Permission to view the underlying entity (customer/job/invoice).
  • Sufficient record data (history, totals, status) for meaningful suggestions.

Step-by-step

Enable insights (admin)

  1. Settings → Integrations → OpenAI → enable and test API key.
  2. Save.

Use on a job

  1. Open Jobs → select a job.
  2. Read AI Insights card (e.g. upsell, recurring customer, pre-job checklist).
  3. Click Refresh after updating job notes or status for new suggestions.

Current limitations

  • Config-gated — without OpenAI, card may show placeholder text or generic tips only.
  • Insights are advisory—not automatic workflow changes.
  • No bulk “insights for all open estimates” report yet.
  • Token/context limits may omit very long job histories.

Roadmap

  • One-click actions from insight (schedule follow-up, create task).
  • Insight feedback (helpful/not) to tune prompts.
  • Manager digest email of high-priority insight flags.

Example: a warning on a job that is not a status change

Open a customer, a job, or an invoice. The AI Insights card lists short items with a title, a body, and a severity of info, warning, or success. Refresh runs again when that control is shown. The badge says AI when OpenAI is connected and Quick tips when it is not. Without a key, the card links to Settings → Integrations → OpenAI and may show only generic tips. It does not rewrite the job, send a text, or create a task.
Insights need enough history on the record to say something specific. A brand-new customer with no jobs produces a thin card. Very long histories can be cut off by context limits. There is no report that runs insights for every open estimate at once. One-click follow-up from a bullet, thumbs-up feedback, and a manager email digest are roadmap, not buttons.
A user who cannot view the customer cannot view the card. Viewing the card does not require the user to accept the suggestion.

Related features