Syncro MCP Prompt Library

Who This is For

This reference document is for operators running prompts through the Syncro MCP connector. There's no custom prompt engineering required. Just copy any prompt below, fill in the bracketed placeholders, and run it.

How placeholders work:

• {curly braces} = required: replace with your value before running
• [square brackets] = optional: include or remove as needed
• Defaults are noted inline where the prompt handles a missing value automatically

New to This? Start Here.

If you're running these prompts for the first time, these three cover the most ground the fastest:

• Tech Queue Triage: see what any tech has open and prioritized in one run
• Unbilled Time/WIP Review: find revenue that hasn't been invoiced yet
• SLA Breach Review: see what's at risk before your standup

Tips for Running These Prompts

• Scoping prompts: Most device health and billing prompts accept {customer}, all customers, or all customers excluding [A, B, C]. An exclusion list is useful for filtering out internal accounts, test clients, or accounts you manage differently.
• Uncertain or missing data: These prompts are written to flag uncertainty rather than guess. If a field is unavailable, the result will include a note rather than silently dropping the row. "Unknown" values in results are intentional signals to verify manually.
• When a tool call fails: You'll see what failed and why rather than a silent stop. Where possible, any prepared content is held so nothing is lost. You can apply it manually or retry once the issue is resolved.
• Chaining prompts: These prompts can be run in sequence in the same session. For example: run the Offline Devices prompt for a customer, then immediately follow with "For the devices flagged as offline, check whether any have open tickets and if not, draft a ticket for each." The prior context carries forward without repeating the data retrieval.
• Combining with skills: If your instance uses reusable skill files, you can invoke them alongside these prompts. Skills handle the multi-step workflow; these library prompts handle the single-session query. When in doubt, start with the prompt and skills layer on top as you build recurring workflows.

When to Run These Prompts

Daily Operations & Triage

Tech Queue Triage

• Prompt: Pull all of {tech name}'s open Syncro tickets, classify them by urgency, and produce a prioritized action report with suggested next steps for each.
• Shorthand that also works: "Check {tech name}'s tickets" / "What does {tech name} have open?" / "Triage {tech name}'s queue"
• What it retrieves: All open tickets assigned to the specified technician, with urgency classification and suggested next steps.
• Example output:
  
• Adapting for a client: Replace {tech name} with any technician's name or "me" if running as yourself. Add "excluding tickets on hold" to filter paused work, or "sorted by customer" to group by account.
• Name resolution note: The tech name must match how the technician appears in Syncro. See MCP Tools Reference if the query returns no results or pulls the wrong person.

SLA Breach Review

• Prompt: Show me all tickets that have breached or are at risk of breaching their SLA target [for {customer} / across all customers / across all customers excluding [A, B, C]]. For each ticket show: ticket number, customer, assigned tech, SLA policy name, breach status (breached or at risk), how long ago the breach occurred or how much time remains, and the ticket subject. Sort breached tickets first, then at-risk tickets, each group sorted by most critical first. For breached tickets, note how long they have been in breach. For at-risk tickets, note how much SLA time remains. After the list, give me a count of breached vs. at-risk tickets per technician so I can see where the pressure is concentrated.
• Shorthand that also works: "What's breaching SLA?" / "SLA status" / "Show me SLA breaches [for {customer}]"
• What it retrieves: Open tickets filtered by SLA status, sorted by breach severity, with a per-technician summary to support dispatch decisions or escalations.
• Example output:
  
• Prerequisites: SLA policies must be configured in Syncro and assigned to ticket types. If your instance doesn't use SLA policies, this prompt will return no results.
• Adapting for a client: Scope to a single customer for an escalation conversation or account review. Run instance-wide at the start of the day or before a standup. Add "include tickets on hold" if paused tickets still count against your SLA clock. Add "only show P1 and P2 priorities" to focus on high-severity breaches.
• Name resolution note: If scoping to a single customer, the name must match the Syncro account name. See also: MCP Tools Reference.

Business Dashboard (Standup View)

• Prompt: Give me a dashboard view of our Syncro instance covering: revenue and aged receivables; work in progress (dollar value of open, non-invoiced tickets); ticket summaries including most time-spent, oldest/stale, and VIP tickets opened in the last 30 days; tech summaries including efficiency rankings, tickets closed, and average ticket time; and asset summaries including devices with more than one ticket in the last 30 days, rework tickets, and most time spent per asset.
• What it retrieves: Financial, ticket, technician performance, and asset data across the entire instance, intended as an executive snapshot at the start of the day or before a leadership standup.
• Example output:
     
• Prerequisites: The VIP tickets section requires priority contacts to be tagged in Syncro. If contact flags aren't configured, that section returns empty. All other sections work regardless.
• Adapting for a client: This prompt is instance-wide by default. Add "for customer {customer}" to scope it to a single account. You can also request individual sections only (e.g., "just the tech summaries" or "just WIP and aged receivables").
• Name resolution note: VIP identification depends on how your instance tags priority contacts. If results are incomplete, see MCP Tools Reference for how priority contact flags are configured.

Onsite Visit Prep

• Prompt: I'm going onsite to customer "{customer}" today. Look up this customer and find all of their tickets that are currently open. From those, identify the ones that involve work needing to be done in person at the customer's location. Infer this from the ticket subject, issue type, and notes (hardware replacement or installs, cabling, physical equipment, or anything a comment indicates has to happen onsite). When it's genuinely unclear whether a ticket is onsite or remote, include it and mark it as uncertain rather than dropping it. Present the results as a table with these columns: ticket number, status, technician assigned, work to be performed (one or two sentence plain summary), and current plan (most recent stated next step from comments or notes, or "No plan documented" if none). Sort by status, then oldest ticket first. After the table, list any ticket that has no assigned technician or no documented plan so I can sort those out before or during the visit.
• What it retrieves: All open tickets for the named customer, filtered to those likely requiring a physical visit, presented as a pre-visit briefing table.
• Example output:
  
• Adapting for a client: Replace {customer} with the client's name. Run the morning of any site visit. Add "also flag any tickets with parts on order" if procurement status is tracked in your instance.
• Name resolution note: The customer name must match the Syncro account name. Partial names usually work, but if results are wrong or empty, see MCP Tools Reference.

Ticket & Dispatch

Create Ticket from Call Transcript

• Prompt: I received a call from {contact name} at {customer}. {One sentence description of the issue.} Create a ticket for it and assign it to {tech name}. Create a private note for {tech name} to reach out to {contact name} ASAP. {Customer} is a [priority / standard] customer. Here is the transcript; create ticket notes from it with next steps: [paste transcript or call recap here]
• What it retrieves/does: Looks up the customer and contact record in Syncro, creates a ticket with structured notes and next steps derived from the transcript, assigns it to the specified technician, and adds a private coaching note.
• Example output:
  
• Adapting for a client: Works for any customer. Omit "priority customer" if it doesn't apply; the designation affects how urgency is framed in the coaching note. If you're working from a call platform recap rather than a raw transcript, paste that instead. The relevant detail will be extracted either way. If you paste a full phone audio transcript, the conversational filler will be discarded automatically.
• Name resolution note: Both the customer name and contact name must resolve in Syncro. If the contact isn't found, the prompt proceeds at the customer level and notes the gap. See also: MCP Tools Reference

Post Call Notes as Private Ticket Comment

• Prompt: Take my call transcript or notes recap with {contact name} [yesterday / on {date}] and post it as a private comment on Syncro ticket {ticket number}. Structure it as: issue reported, troubleshooting already attempted, environment details, and next steps.
• What it retrieves/does: Takes a call recap and posts it as a hidden private comment on the specified ticket, structured for the next technician who picks it up.
• Example output:
  
• Adapting for a client: Add "make it a public comment" if you want it visible to the customer. Add "also update the ticket status to In Progress" if you want the status changed at the same time.
• Name resolution note: The ticket number must be exact. Contact name is used for context only and does not need to resolve in Syncro.

Billing & Time

Labor Log from Work Notes

• Prompt: Summarize the following notes and create a billable labor log entry formatted for a Syncro timer. List every unique action in outcome-focused, client-facing language. Do not include specific commands or steps the customer could repeat themselves such as CLI commands or tool names a client could use independently. [paste work notes, call recap, or ticket comments here]
• Optional addition to post directly: "Post this as a timer comment on ticket {ticket number}."
• What it retrieves/does: Converts raw work notes or call recaps into a clean, pipe-separated labor log entry in client-facing language without internal commands exposed. If posting to a ticket, writes the entry as a timer comment.
• Example output:
  
• Adapting for a client: For a verbose private version instead of a client-facing log, add: "Write this as a private comment for a future technician. Include full detail including commands and steps."
• Name resolution note: No name resolution required unless posting to a ticket. See MCP Tools Reference for ticket number formatting.

Unbilled Time/WIP Review

• Prompt: Show me all open tickets that have logged time but have not been invoiced. For each ticket show: ticket number, customer, assigned tech, total hours logged, most recent work date, and ticket subject. Sort by total hours descending so the largest unbilled items are at the top. At the end, give me a total estimated dollar value of unbilled time [using our standard labor rate of ${rate}/hr and flag it as an estimate if rates vary by tech or customer].
• Shorthand that also works: "What time hasn't been invoiced?" / "Show me WIP" / "Unbilled time for {customer}"
• What it retrieves: Open tickets with unbilled logged time, sorted by hours, with a WIP dollar estimate.
• Example output:
  
• Adapting for a client: Add "for customer {customer}" to scope to a single account. This is useful before a billing conversation or to catch missed charges before invoicing. Remove the dollar total line if billing rates aren't uniform enough to make the estimate meaningful.
• Name resolution note: If scoping to a single customer, the name must match the Syncro account. See also: MCP Tools Reference.

Invoice Description from Vendor Billing Data

• Prompt: Format this for a Syncro invoice description. Group by service, shorten verbose vendor SKU names to readable abbreviations, apply [our standard markup of X%], and sort categories by spend descending. [paste vendor billing data here e.g., usage detail, invoice line items, or recurring charges]
• Optional addition to post directly: "Write this to invoice {invoice number} description field."
• What it retrieves/does: Converts raw vendor billing exports into a clean, readable invoice description block formatted for the Syncro invoice description field.
• Example output:
  
• Adapting for a client: Specify your markup percentage if it varies by customer or isn't in your system prompt. Add "start with a one-line summary of total charges before the detail" if you want a summary line at the top of the description.
• Name resolution note: No name resolution required unless posting to an invoice. See also: MCP Tools Reference.

Reporting & QBR

Quarterly Business Review

• Prompt: Build a Quarterly Business Review for {customer} covering {quarter: default to the most recently completed calendar quarter}. Pull the relevant tickets, time entries, and asset data for this customer over that period and produce a presentation-ready summary I can walk a client through. Write in plain professional language aimed at a business decision-maker, not a technician; explain significance rather than just listing numbers. Cover these sections in order: (1) Executive summary — three or four sentences on overall service activity, anything notable, and the general health of their environment. (2) Service activity — tickets opened and closed, breakdown by category or type, total support time delivered, and whether volume changed from the prior quarter if that data is available. (3) Notable issues and resolutions — the most significant tickets or recurring problems this quarter, what they were, and how they were handled. (4) Environment and asset health — current state of managed devices including total assets, anything offline or unhealthy, devices out of warranty or approaching end of warranty, and any EOL operating systems or hardware, framed as awareness items. (5) Recommendations and roadmap — a short prioritized list of suggested next steps tied back to something concrete from the quarter. Base every section on actual data for this customer. Do not invent metrics or incidents to fill out a section. If a section has little supporting data, state that plainly rather than padding it. Flag any data quality issues at the end as notes for me, not for the client.
• Shorthand that also works: "Build a QBR for {customer}" / "QBR {customer} {quarter}"
• What it retrieves: Ticket history, time entries, and asset data for the customer over the specified quarter, synthesized into a full QBR document in plain business language.
• Example output:

• Adapting for a client: Replace {quarter} with the specific period (e.g., "Q1 2026" or "January through March 2026"). You can request individual sections only (e.g., "just the recommendations section for {customer} Q1"). Add "format this as a Word document I can share" to get an exportable version.
• Name resolution note: The customer name must match the Syncro account name exactly. This is especially important for multi-location or multi-account clients where similar names may exist. Incorrect name resolution will result in incomplete or misattributed QBR data. See also: MCP Tools Reference.