ServiceTitan

Yes. ServiceTitan integrates with IgnitePOST for automated handwritten mail. The connection runs on a scheduled ServiceTitan report delivered to a dedicated IgnitePOST user in your account, so there are no API credentials to manage, no Zapier subscription required, and no developer involved. Setup takes about 30 minutes. Once it is live, cards trigger off any report you can build in Report Builder: unsold estimates, completed jobs, membership enrollments, renewal windows. Cards ship within 24 to 48 hours.

How the integration actually works

Most direct mail vendors connect to ServiceTitan through the API, which means credentials, scopes, a developer, and something that breaks quietly when a token expires.

IgnitePOST uses a different mechanism, and for most contractors it is the better one: ServiceTitan's own scheduled reporting delivers your trigger list to IgnitePOST on a recurring basis.

You create an IgnitePOST user inside ServiceTitan, build a report that returns the customers who should receive a card, and schedule that report to deliver daily. IgnitePOST receives it, matches the columns, and queues the cards. Nobody in your office touches anything after setup.

The advantages are practical: you build and change triggers yourself in Report Builder without a developer, the permissions live inside ServiceTitan where your admin can see and revoke them, and there is no middleware bill. The tradeoff is that it is batch rather than real time. A daily schedule means a card is queued within 24 hours of the event rather than within seconds. For mail that will spend three days in the postal system, that difference does not matter.

Setup, step by step

Step 1: Create the IgnitePOST user in ServiceTitan

Go to Settings → Employees → Add Employee/User.

Create the user with an email address in this format, substituting your company name with no spaces:

datalists+YourCompanyName@ignitepost.com

Grant the user reporting access and data export permissions. It needs nothing else: no dispatch, no accounting, no customer record editing.

Step 2: Build the report that defines your trigger

In Report Builder, create a report returning the customers who should receive a card. These fields are required:

• Customer Name
• Address Line 1
• Address Line 2
• City
• State
• Zipcode
• Customer Email

These fields are optional and are used for personalization and routing:

• Jobs Total, to route high-ticket customers to a different card design or message
• Technician, to sign the card from the person who was actually in the house, which measurably outperforms a generic company signature
• Creative / Card Design, to select which card template this row should use

Any additional column you include can be merged into the card copy, which is how you get specifics like the job type or the equipment installed into the handwriting.

Step 3: Schedule the delivery

On the saved report, set up a schedule:

• Recipient: the datalists+YourCompanyName@ignitepost.com user you created
• Frequency: daily is recommended for event-driven triggers; weekly or monthly is fine for renewal and reactivation lists
• Format: Excel (.XLSX) or CSV
• Subject line: Company Name - Report Name - Date Range

The subject line convention matters. It is how IgnitePOST tells your triggers apart when you are running several, so keep it consistent.

Step 4: Confirm the first run

Let the first scheduled delivery run and confirm with your IgnitePOST contact that the columns mapped correctly before you approve cards to send. Check the row count against what you expect. A report that returns 4,000 rows on day one when you expected 40 usually means the date filter is measuring the wrong field.

The five ServiceTitan reports worth building first

1. Unsold estimates

Filter: estimates in Presented status, older than 1 day, with no linked sold job. Schedule daily.

This is the highest-return trigger for nearly every trade, and the one Mr. Electric of Boulder ran to generate over $28,000 in completed job revenue from 55 cards and roughly $150 of spend in under two months.

2. Completed jobs, filtered by job type

Filter: jobs in Completed status within the last day, with a job type filter. Schedule daily.

The job type filter is the part people skip and regret. Without it you will send the same card after a $90 service call and a $14,000 install. Decide which job types deserve a card and which do not before you turn this on.

3. New membership enrollments

Filter: memberships created in the last day. Schedule daily.

The welcome card is the cheapest retention intervention available and it belongs in week one, not month three.

4. Memberships approaching renewal

Filter: memberships with an expiration date 45 days out. Schedule weekly.

Ahead of the auto-renew charge, not after it.

5. Recall list: no service in 18 months

Filter: customers with no completed job in 18 months and a valid mailing address. Schedule monthly or run as a quarterly one-off.

This is dormant revenue sitting in a system you already pay for.

Practical notes that will save you a support ticket

Clean the addresses before the first send. Most ServiceTitan instances carry 8 to 12% stale addresses, and every one of them is a card you pay for and nobody reads. Run NCOA on your customer file before you scale the program.

Watch for duplicate customer records. If a household exists twice in ServiceTitan, they will get two cards. Deduplicate on address, not on name. "Robert Chen" and "Bob Chen" at the same address are one mailbox.

Use the Technician field. A card signed by the tech who was in the house reads completely differently from one signed by the company. It is one optional column and it is the single highest-return personalization available in this integration.

Set the date filter on the right field. Estimate presented date, job completed date, and membership created date are different columns, and choosing the wrong one is the most common reason a first run returns an unexpected row count.

Start with one report. Get unsold estimates working and measured before you add four more triggers. Contractors who turn on five at once cannot tell which one is producing the return.

What the integration does not do

Stated plainly, so nothing is a surprise:

• It is not real time. A daily schedule means the card queues within 24 hours of the event, not within seconds. Combined with a 24 to 48 hour ship time and postal transit, plan on the card landing three to six days after the trigger.
• It does not write back to ServiceTitan. Card sends do not currently appear as an activity on the ServiceTitan customer record. If you need attribution inside ServiceTitan, the practical approach is a dynamic QR code per recipient and reconciling on your side.
• It does not deduplicate against your other marketing. If a customer is also in an email nurture and an SMS sequence, the card is additive, not coordinated. Decide your total contact cadence deliberately.
• It does not validate addresses for you. Garbage in, mailed garbage out. See the NCOA note above.

Frequently asked questions

Does ServiceTitan integrate with handwritten mail?

Yes. IgnitePOST connects to ServiceTitan through ServiceTitan's native scheduled reporting: you create an IgnitePOST user in your account, build a report in Report Builder defining who should receive a card, and schedule it to deliver daily. Cards ship within 24 to 48 hours of the report arriving. No API credentials, no Zapier subscription and no developer are required, and setup takes about 30 minutes.

Do I need the ServiceTitan API to use IgnitePOST?

No. The standard integration uses scheduled reports, which is why most contractors can set it up themselves. A direct API with unlimited calls is available on every IgnitePOST plan if you would rather build against it.

Does this require a Zapier subscription?

Not for ServiceTitan. Zapier is how other platforms such as Housecall Pro and Jobber connect; ServiceTitan uses its own reporting instead.

How long does setup take?

Roughly 30 minutes for the first trigger: create the user, build the report, schedule it, and confirm the first run mapped correctly. Additional triggers are a few minutes each once the user exists.

What ServiceTitan fields does IgnitePOST need?

Required: Customer Name, Address Line 1 and 2, City, State, Zipcode, and Customer Email. Optional but useful: Jobs Total, Technician, and Creative or Card Design. Any extra column can be merged into the card copy.

How often should the report run?

Daily for event-driven triggers like unsold estimates and completed jobs. Weekly is enough for renewal windows, and monthly or quarterly for recall and reactivation lists.

How fast do cards go out after the report arrives?

Typically 24 to 48 hours to ship, postmarked from Boston, MA by default. Allowing for postal transit, the card generally lands three to six days after the triggering event.

Can I send different cards for different job types?

Yes. Include a Creative or Card Design column in the report, or build separate reports per job type with distinct subject lines. Routing by Jobs Total is a common approach for separating high-ticket customers from routine service calls.

What does it cost?

There is no fee for the integration itself. You pay per card: $1.75 to $4.39 on prepaid plans depending on volume, or a subscription starting at $109 a month for 300 cards a year. Card stock, envelope, full-color printing and First Class postage are included.

‍