The Customer Factor API and MCP server Let your AI agent schedule the route and send the bills.

ToolWhat it doesAccess

• find_customers Search customers and prospects, or open one customer profile. read

  Uses the global search at the top of the screen. Most other tools take a customer, so this is usually the first call. Nothing is changed, so it runs without asking.

  MCP callthe_customer_factor_read → find_customers

  REST endpointGET https://cotlet.dev/api/v1/the-customer-factor/customers/find

  Parameters

  Parameters: find_customers

  Name	Type	Description
  query string required	string	Last name, first name, address or phone number, as the global search takes them.
  profile boolean	boolean	Return the full profile of the best match: job locations, recurring jobs, currently scheduled jobs and notes.

  Example input

  {
    "query": "query"
  }

  Example response

  {
    "customers": [
      {
        "customer": "Example Homeowner",
        "type": "Residential",
        "address": "12 Oak Lane, Springfield",
        "phone": "+1 555 0100",
        "recurring_jobs": 1
      }
    ]
  }

• add_customer Add a customer under Customers > Add, residential or commercial. writeAsks first

  Choose residential or commercial first, as the Help Center asks; it decides the billing and service details applied. Run find_customers first so the same household is not added twice. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → add_customer

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/customers

  Parameters

  Parameters: add_customer

  Name	Type	Description
  type string required	string	`residential` or `commercial`.
  fields object required	object	Full name or company, address, phone, email and the other customer fields you want set.

  Example input

  {
    "type": "type",
    "fields": "fields"
  }

  Example response

  {
    "customer": "Example Homeowner",
    "type": "Residential",
    "address": "12 Oak Lane, Springfield",
    "saved": true
  }

• add_prospect Add a lead as a residential or commercial prospect, without an estimate yet. writeAsks first

  The prospect gets its own profile, ready for a Big Proposal or an estimate. convert_prospect makes it a customer later. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → add_prospect

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/prospects

  Parameters

  Parameters: add_prospect

  Name	Type	Description
  type string required	string	`residential` or `commercial`.
  fields object required	object	Full name, address and contact details.

  Example input

  {
    "type": "type",
    "fields": "fields"
  }

  Example response

  {
    "prospect": "Sample Office Park",
    "type": "Commercial",
    "saved": true
  }

• convert_prospect Make a prospect a customer with the "Make 'em A Customer" button. writeAsks first

  Scheduling a job from an estimate with schedule_job converts the prospect automatically; this tool is for the manual case. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → convert_prospect

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/prospect/convert

  Parameters

  Parameters: convert_prospect

  Name	Type	Description
  prospect string required	string	Prospect name, as find_customers returns it.

  Example input

  {
    "prospect": "prospect"
  }

  Example response

  {
    "customer": "Sample Office Park",
    "status": "customer"
  }

• add_job_location Add another service address to a customer profile. writeAsks first

  For a rental home, a business address or a commercial customer with several sites. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → add_job_location

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/job-locations

  Parameters

  Parameters: add_job_location

  Name	Type	Description
  customer string required	string	Customer name, address or phone, as find_customers returns it.
  type string	string	`residential` or `commercial`. Defaults to the customer's type.
  address object required	object	Address, address 2, city, state and postal code.
  bill_to boolean	boolean	Use this location as the Bill To address on invoices, work orders and estimates.
  bill_to_name string	string	A different Bill To name, if needed.

  Example input

  {
    "customer": "customer",
    "address": "address"
  }

  Example response

  {
    "customer": "Example Homeowner",
    "location": "48 Lake Road, Springfield",
    "type": "Residential",
    "bill_to": false,
    "saved": true
  }

ToolWhat it doesAccess

• schedule_job Schedule a single job on a customer's Schedule Job sub-tab. writeAsks first

  Scheduling from a prospect's estimate converts the prospect to a customer, as the Help Center describes. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → schedule_job

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/job/schedule

  Parameters

  Parameters: schedule_job

  Name	Type	Description
  customer string required	string	Customer name, address or phone, as find_customers returns it.
  date string required	string	ISO date.
  time string	string	Appointment time or range, and duration.
  job_type string required	string	Job type from manage_job_types.
  price number	number	Price in the "each" field.
  assigned_to string	string	Employee for the job.
  frequency_period string	string	Optional: how often the customer wants service, so The Customer Factor prompts you to reach out near the next date.
  create_invoice boolean	boolean	Use "Schedule & Create Invoice" instead of "Schedule".

  Example input

  {
    "customer": "customer",
    "date": "date",
    "job_type": "job type"
  }

  Example response

  {
    "customer": "Example Homeowner",
    "date": "2026-11-20",
    "time": "09:00-11:00",
    "job_type": "Window cleaning, exterior",
    "price": 180,
    "assigned_to": "Crew A",
    "scheduled": true
  }

• schedule_recurring_job Schedule a job that repeats by week or by month, with months left out if needed. writeAsks first

  The job then appears under Recurring Job(s) on the customer profile and keeps going until it ends. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → schedule_recurring_job

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/recurring-job/schedule

  Parameters

  Parameters: schedule_recurring_job

  Name	Type	Description
  customer string required	string	Customer name, address or phone, as find_customers returns it.
  first_date string required	string	ISO date of the first visit.
  job_type string required	string	Job type from manage_job_types.
  price number	number	Price per visit.
  assigned_to string	string	Employee for the job.
  period string required	string	A weekly period (every week, every other week) or a monthly one (first Monday of the month), as the recurring options offer.
  exclude_months array	array	Months with no service, for example a slow season.
  ends string	string	End date. Defaults to Never.

  Example input

  {
    "customer": "customer",
    "first_date": "first date",
    "job_type": "job type",
    "period": "period"
  }

  Example response

  {
    "customer": "Example Homeowner",
    "job_type": "Window cleaning, exterior",
    "period": "every 4 weeks",
    "exclude_months": [
      "December",
      "January",
      "February"
    ],
    "ends": "Never",
    "scheduled": true
  }

• update_recurring_job Change the price, period or services of a recurring job, or delete it. writeAsks first

  A change applies to every future job of that customer. Deleting removes only future jobs; past jobs stay. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → update_recurring_job

  REST endpointPATCH https://cotlet.dev/api/v1/the-customer-factor/recurring-job

  Parameters

  Parameters: update_recurring_job

  Name	Type	Description
  customer string required	string	Customer name, address or phone, as find_customers returns it.
  job string required	string	The recurring job, by job type.
  changes object	object	New price, period or added service.
  delete boolean	boolean	Delete the recurring job.

  Example input

  {
    "customer": "customer",
    "job": "job"
  }

  Example response

  {
    "customer": "Example Homeowner",
    "job": "Window cleaning, exterior",
    "price": 190,
    "applies_to": "future jobs",
    "saved": true
  }

• put_job_on_hold Put a scheduled job on hold, with a reason. writeAsks first

  The job moves to the On Hold area of the calendar. For a recurring job the agent asks whether to hold this visit or all of them. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → put_job_on_hold

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/job-on-hold/put

  Parameters

  Parameters: put_job_on_hold

  Name	Type	Description
  customer string required	string	Customer name, address or phone, as find_customers returns it.
  date string required	string	ISO date of the job.
  reason string	string	Why the job is on hold.
  all_recurring boolean	boolean	For a recurring job: hold all of them instead of this one only.

  Example input

  {
    "customer": "customer",
    "date": "date"
  }

  Example response

  {
    "customer": "Example Homeowner",
    "date": "2026-11-20",
    "status": "on hold",
    "reason": "Customer away",
    "all_recurring": false
  }

• mark_job_completed Change a job's status from Open to Completed. writeAsks first

  Completed jobs fade on the daily calendar and are struck through on the weekly and monthly ones. Set it back to Open with the same tool if it was a mistake. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → mark_job_completed

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/job-completed/mark

  Parameters

  Parameters: mark_job_completed

  Name	Type	Description
  customer string required	string	Customer name, address or phone, as find_customers returns it.
  date string required	string	ISO date of the job.

  Example input

  {
    "customer": "customer",
    "date": "date"
  }

  Example response

  {
    "customer": "Example Homeowner",
    "date": "2026-11-20",
    "job_type": "Window cleaning, exterior",
    "status": "Completed"
  }

ToolWhat it doesAccess

• manage_job_types List, add, edit or delete job types and job packages. writeAsks first

  Job types fill the dropdown when you schedule an estimate or a job. Run `list` first so the list does not grow duplicates. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → manage_job_types

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/job-types/manage

  Parameters

  Parameters: manage_job_types

  Name	Type	Description
  action string required	string	`list`, `create`, `update` or `delete`. `list` only reads.
  name string	string	Job type or package name.
  package_items array	array	For a package: the items it covers.
  price number	number	Package price, for example a whole house special.

  Example input

  {
    "action": "action"
  }

  Example response

  {
    "job_types": [
      "Window cleaning, exterior",
      "Screen cleaning",
      "Gutter cleaning"
    ],
    "packages": [
      {
        "name": "Whole house special",
        "price": 99
      }
    ]
  }

• create_job_checklist Create a job checklist with to-do items for chosen job types and customers. writeAsks first

  Once saved, the checklist shows next to every matching job in the software and the mobile app, where technicians tick items and leave notes. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → create_job_checklist

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/job-checklists

  Parameters

  Parameters: create_job_checklist

  Name	Type	Description
  title string required	string	Checklist title.
  job_types array required	array	Job types it applies to, or `All jobs`.
  customers array	array	Specific customers, or leave empty for All Customers.
  items array required	array	The to-do items.

  Example input

  {
    "title": "title",
    "job_types": "job types",
    "items": "items"
  }

  Example response

  {
    "checklist": "Exterior window clean",
    "job_types": [
      "Window cleaning, exterior"
    ],
    "items": 4,
    "saved": true
  }

ToolWhat it doesAccess

• search_invoices Search the Invoices tab, for example all unpaid invoices of one customer. read

  Returns invoice number, customer, date, amount and paid status. Use it before record_payment or email_payment_reminders. Read only, it runs without asking.

  MCP callthe_customer_factor_read → search_invoices

  REST endpointGET https://cotlet.dev/api/v1/the-customer-factor/invoices/search

  Parameters

  Parameters: search_invoices

  Name	Type	Description
  status string	string	`unpaid`, `paid` or empty for all.
  customer string	string	Customer last name or company name.

  Example response

  {
    "invoices": [
      {
        "invoice": 1187,
        "customer": "Example Homeowner",
        "date": "2026-11-03",
        "amount": 235.4,
        "status": "unpaid"
      },
      {
        "invoice": 1192,
        "customer": "Example Homeowner",
        "date": "2026-11-10",
        "amount": 150,
        "status": "unpaid"
      }
    ]
  }

• create_invoice Create one invoice from one or more scheduled jobs of a customer, with or without tax. writeAsks first

  Ticks the jobs under Invoice Status and clicks Create Invoice. The agent shows you the jobs and total before saving; email_invoice sends it. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → create_invoice

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/invoices

  Parameters

  Parameters: create_invoice

  Name	Type	Description
  customer string required	string	Customer name, address or phone, as find_customers returns it.
  jobs array required	array	Scheduled jobs to invoice, by date and job type, from Currently Scheduled Jobs.
  tax_percent number	number	Tax percentage. Leave empty for no tax.

  Example input

  {
    "customer": "Example Homeowner",
    "jobs": [
      {
        "date": "2026-11-20",
        "job_type": "Window cleaning, exterior"
      },
      {
        "date": "2026-11-20",
        "job_type": "Screen cleaning"
      }
    ],
    "tax_percent": 7
  }

  Example response

  {
    "invoice": 1203,
    "customer": "Example Homeowner",
    "lines": [
      {
        "job": "Window cleaning, exterior",
        "amount": 180
      },
      {
        "job": "Screen cleaning",
        "amount": 40
      }
    ],
    "tax_percent": 7,
    "total": 235.4,
    "status": "unpaid"
  }

• email_invoice Email an invoice to the customer, with an optional discount. writeAsks first

  The invoice goes to the customer's inbox, so the agent shows the total and recipient first. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → email_invoice

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/invoice/email

  Parameters

  Parameters: email_invoice

  Name	Type	Description
  invoice integer required	integer	Invoice number.
  discount string	string	A dollar amount or a percentage, for example `10%`.
  template string	string	Invoice email template from create_email_template.

  Example input

  {
    "invoice": 1
  }

  Example response

  {
    "invoice": 1203,
    "to": "homeowner@example.com",
    "total": 235.4,
    "sent": true
  }

• add_invoice_deposit Add a deposit to an invoice, as a dollar amount or a percentage. writeAsks first

  Saves with Update. The deposit due then shows on the invoice when you email it. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → add_invoice_deposit

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/invoice-deposits

  Parameters

  Parameters: add_invoice_deposit

  Name	Type	Description
  invoice integer required	integer	Invoice number.
  deposit string required	string	For example `$50` or `25%`.

  Example input

  {
    "invoice": 1,
    "deposit": "deposit"
  }

  Example response

  {
    "invoice": 1210,
    "total": 900,
    "deposit": "25%",
    "deposit_due": 225,
    "saved": true
  }

• record_payment Record a payment on one invoice, or one payment for several unpaid invoices. writeAsks first

  Records the payment and marks paid invoices with the Paid stamp. It does not charge a card; card processing through Square, Stripe or Worldpay stays in The Customer Factor's own payment window. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → record_payment

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/payments

  Parameters

  Parameters: record_payment

  Name	Type	Description
  invoices array required	array	Invoice numbers, all from the same customer.
  amount number required	number	Amount paid, full or partial.
  method string required	string	Form of payment, for example check or cash.
  reference string	string	Check number or other reference.
  date string	string	ISO date. Defaults to today.

  Example input

  {
    "invoices": "invoices",
    "amount": 1,
    "method": "method"
  }

  Example response

  {
    "invoices": [
      1187,
      1192
    ],
    "amount": 385.4,
    "method": "check",
    "reference": "2045",
    "status": "Paid"
  }

• email_payment_reminders Email payment reminders for selected unpaid invoices. writeAsks first

  Reminders reach your customers, so the agent lists who gets one before it sends. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → email_payment_reminders

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/payment-reminders/email

  Parameters

  Parameters: email_payment_reminders

  Name	Type	Description
  invoices array	array	Invoice numbers. Leave empty for every unpaid invoice.
  exclude_customers array	array	Customers to leave out.
  message string	string	Reminder text. Leave empty for the template in Payment Reminder Settings.

  Example response

  {
    "reminders": 2,
    "customers": [
      "Example Homeowner",
      "Sample Office Park"
    ],
    "sent": true
  }

• send_customer_statements Email or print statements for a period, for one customer or many. writeAsks first

  A statement lists the customer's invoices of the period. Bulk sending is supported, so the agent shows the customer count first. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → send_customer_statements

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/customer-statements

  Parameters

  Parameters: send_customer_statements

  Name	Type	Description
  period string required	string	For example `This Month`, or a date range.
  customers array	array	Customers. Leave empty for everyone with invoices in the period.
  output string	string	`email` or `print`.

  Example input

  {
    "period": "period"
  }

  Example response

  {
    "period": "This Month",
    "statements": 2,
    "output": "email",
    "sent": true
  }

ToolWhat it doesAccess

• create_big_proposal Create a multi-page Big Proposal in one of the online and PDF formats. writeAsks first

  When a prospect or customer clicks Accept, The Customer Factor emails you. You can keep several, for example one for residential and one for commercial. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → create_big_proposal

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/big-proposals

  Parameters

  Parameters: create_big_proposal

  Name	Type	Description
  name string required	string	Proposal name, for example Commercial window cleaning.
  format string	string	One of the five online formats; the Help Center recommends Format 5.
  color string	string	One of the ten colors or a custom color.
  pages array	array	Pages to include, for example photos, W9 or license.

  Example input

  {
    "name": "Jane Doe"
  }

  Example response

  {
    "proposal": "Commercial window cleaning",
    "format": "Format 5",
    "pages": [
      "About us",
      "Photos",
      "W9",
      "License"
    ],
    "saved": true
  }

• add_task Add a task from Quick Add, optionally assigned and repeating. writeAsks first

  An assigned task is work for a teammate, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → add_task

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/tasks

  Parameters

  Parameters: add_task

  Name	Type	Description
  title string required	string	Task title.
  assigned_to string	string	Who the task is for.
  description string	string	Optional details.
  date string required	string	ISO date and time.
  repeat string	string	Repeat rule, if the task repeats.

  Example input

  {
    "title": "title",
    "date": "date"
  }

  Example response

  {
    "task": "Call Sample Office Park about spring start",
    "assigned_to": "Office",
    "date": "2026-11-21T10:00",
    "saved": true
  }

• edit_specific_note Add or edit a private Specific Note on a customer profile. writeAsks first

  Specific Notes are for the main user and admins, not for customers. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → edit_specific_note

  REST endpointPATCH https://cotlet.dev/api/v1/the-customer-factor/specific-note

  Parameters

  Parameters: edit_specific_note

  Name	Type	Description
  customer string required	string	Customer name, address or phone, as find_customers returns it.
  date string	string	Date of the note to edit. Leave empty to add a new one.
  note string required	string	Note text.

  Example input

  {
    "customer": "customer",
    "note": "note"
  }

  Example response

  {
    "customer": "Example Homeowner",
    "date": "2026-11-14",
    "note": "Gate code changed, ask before arrival.",
    "saved": true
  }

• create_email_template Create an estimate or invoice email template, from a sample if you like. writeAsks first

  Templates are used every time you email an estimate or invoice, so a new one waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → create_email_template

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/email-templates

  Parameters

  Parameters: create_email_template

  Name	Type	Description
  kind string required	string	`estimate` or `invoice`.
  title string required	string	Template title, seen only by you.
  sample string	string	A sample to start from, for example "Email w/o pdf attachment (Recommended)" or "Include Credit Card button".
  subject string	string	Subject, if not from a sample.
  message string	string	Message, with % personalization tokens if you like.

  Example input

  {
    "kind": "kind",
    "title": "title"
  }

  Example response

  {
    "kind": "invoice",
    "title": "Invoice Template",
    "sample": "Include Credit Card button",
    "saved": true
  }

ToolWhat it doesAccess

• message_employees Send an email or SMS to selected employees from Manage Employees. writeAsks first

  Messages reach your team, so the agent shows recipients and text before sending. By default you confirm each call; you can switch that off for this tool.

  MCP callthe_customer_factor_write → message_employees

  REST endpointPOST https://cotlet.dev/api/v1/the-customer-factor/employees/message

  Parameters

  Parameters: message_employees

  Name	Type	Description
  employees array required	array	Employees, or `all`.
  channel string required	string	`email` or `sms`.
  message string required	string	Message text.

  Example input

  {
    "employees": "employees",
    "channel": "channel",
    "message": "message"
  }

  Example response

  {
    "channel": "sms",
    "employees": [
      "Crew A",
      "Crew B"
    ],
    "sent": true
  }