Ascora

@Ascora show me all customers added in the last 30 days, sorted by creation date

Based on the Ascora customer list, here are 12 customers added since December 15th: ABC Plumbing (Dec 16), Green Valley HVAC (Dec 18), Metro Construction Ltd (Dec 20), and 9 others. Each entry includes contact details, account status, and assigned sales rep. The most recent addition is Riverside Mechanical, created yesterday with primary contact Sarah Chen. All accounts are currently active with standard payment terms.

This example demonstrates the Get Customers tool with date filtering. Note that Ascora's API requires a valid API key with read permissions on customer records. Response pagination may apply for accounts with large customer databases—this example assumes under 100 results.

@Ascora create a quotation for customer ID 4782 covering HVAC maintenance package, annual contract at $2400

I've created quotation #Q-2025-0089 in Ascora for customer ID 4782. The quote includes the annual HVAC maintenance package at $2,400.00, with line items for quarterly inspections, filter replacements, and priority service response. The quotation is now in 'Draft' status and visible in the customer's account. You can finalize pricing or add additional line items before sending it to the customer for approval.

This showcases the Create Quotation tool's write capability. Important: creating quotations requires API key permissions for quote management, and the customer ID must exist in your Ascora account. The tool creates a draft—you'll need to manually approve or send it through Ascora's interface.

@Ascora pull all open jobs assigned to technician 'Mike Torres' and summarize which ones are overdue

Mike Torres currently has 8 open jobs in Ascora. Of these, 3 are past their scheduled completion date: Job #J-5521 (commercial boiler repair, 2 days overdue), Job #J-5498 (ductwork inspection, 5 days overdue), and Job #J-5467 (emergency callout follow-up, 1 day overdue). The remaining 5 jobs are scheduled for this week and next. The overdue jobs represent approximately $4,200 in pending invoicing once completed.

This example combines the Get Jobs tool with AI synthesis to identify scheduling issues. The MCP retrieves raw job data filtered by technician assignment; the AI layer interprets due dates and calculates overdue status. Requires API access to job records and assumes your Ascora account tracks technician assignments.

When Ascora MCP speeds up same-day quote generation

A 6-person HVAC company uses Switchy to draft quotes during site visits. The technician describes the job in chat, the AI pulls the customer record via Get Customers, checks open jobs with Get Jobs, and fires Create Quotation with line items and labor estimates. The MCP handles the round-trip in under 10 seconds, so the quote lands in the customer's inbox before the tech leaves the property. This works because Ascora's API key auth is simple and the 5-tool scope stays narrow—no risk of the AI wandering into billing or inventory. If your quoting process needs approval layers or custom pricing logic, you'll still need a human step between the draft and the send.

Bulk customer deletion when migrating CRM data

A 3-person property maintenance startup is moving from Ascora to a new platform and needs to archive 200+ duplicate or test customer records before the cutover. They load a CSV of customer IDs into Switchy, and the AI loops through Delete Customer calls in batches of 20, pausing to confirm each batch before proceeding. The MCP's API key auth means no OAuth dance, and the narrow tool set keeps the AI from touching job or invoice data. This scenario only makes sense if you're confident in your deletion list—Ascora's API doesn't offer an undo, so a bad CSV wipes records permanently. For ongoing CRM hygiene, manual review beats automation.

Using Get Jobs to prep daily field assignments

A 10-person plumbing company's dispatcher opens Switchy at 7 AM and asks for today's job list filtered by region and priority. The AI calls Get Jobs with date and status filters, then formats the results into a readable rundown with customer names (via Get Customers) and job notes. The dispatcher copies the summary into Slack for the field team. This works because the MCP's 5 tools cover the read-only lookup the dispatcher needs, and API key auth means no per-user login friction. If your job volume exceeds 100 per day, the pagination in Get Jobs gets clunky—you'll want a dedicated dashboard instead of a chat interface.