A solutions engineer for every account.

A solutions engineer for every account.

The Solutions Engineer agent is the technical point of contact for every live account. It keeps integrations healthy, answers API and configuration questions, moves customers through upgrades and passes real bugs to your engineers with everything they need.

SE
Solutions Engineerto Jordan, Lead developer
Sent
Moving your integration to API v2

Hi Jordan, v1 of our API retires in 90 days. Your integration uses two endpoints that change: /contacts and /events.

The attached guide covers just those two, with the new request formats. Reply here if anything’s unclear.

v2-migration-guide.pdfPDF

Example: API deprecation

Every account upgraded before anything breaks.

Here’s how the agent moves customers off a retiring API version.

01

Find

When you announce a retiring version, it finds every account still using it and the endpoints each one calls.

02

Guide

Emails each technical contact a migration guide built for their integration, with only the changes that affect them.

03

Follow up

Sends reminders and confirms each migration from usage data, without anyone on your team chasing.

04

Track

Every Monday your team gets a migration tracker in Slack, with accounts at risk flagged for a person.

Answers technical questions on the spot.

In Slack or by email

Customers ask in your shared Slack channel or by email, and get an answer in minutes, not days.

From your docs and API reference

Answers come from your documentation and known fixes, the way your engineers would answer.

A screen-share when it helps

For a tricky configuration, the agent joins a call, sees their setup and fixes it with them.

# shared-supportSlack
LD
Lead developerWebhook signatures started failing this morning. Did something change on your side?
SE
Solutions EngineerKuluYes, signing secrets were rotated yesterday. Copy the new secret from Settings, Webhooks and the next delivery will pass. Steps are in the doc below.
webhook-rotation.pdfPDF

app.yourproduct.com/integrations

Viewing

Integrations

CRM sync paused

Reconnect

Your CRM access expired last night, so syncs have stopped. Click Reconnect and approve access to resume.

Spots failing integrations before customers do.

Watches every integration

Webhooks and product events show failed syncs and errors the moment they start.

A diagnosis, not an alert

The admin gets an email with what broke, why, and the exact steps to fix it.

Fixed with them if needed

If they’re stuck, the agent offers a screen-share and works through the fix on their setup.

A technical review for every account.

Every quarter, on schedule

Each account gets a review of its integrations, error trends and setup, every quarter.

Recommendations that fit

Capabilities they aren’t using yet, and changes that would make their setup more reliable.

Sent as a PDF

The review goes to the technical contact by email, and your team gets a copy.

Technical review · Q3

Quarterly

Done

Integrations and error trends

Done

API capabilities not in use

Now

Writing recommendations

Working from

API docs

Product events

CRM

Building the review PDF…

# engineeringSlack
SE
Solutions EngineerKuluBug on the 40-seat account: CRM sync fails on custom fields since Monday. Reconnecting and re-mapping didn’t fix it. Contacts aren’t syncing, so their weekly reports are empty. Logs and config attached.
E
EngineerOn it. Thanks for the repro steps.

Your engineers only see what needs them.

When something is a real bug, the agent packages it for your engineers in Slack: the account, the error, the steps already tried and the impact.

Fewer tickets for your team

Common setup and integration problems are solved before they reach engineering.

Escalations with everything attached

Logs, configuration and the customer’s history arrive together.

Patterns you can fix at the source

Every question and fix is logged, so you can see what comes up most and fix it in the product.

The Kulu difference

The Kulu difference

The Kulu difference

The Kulu difference

Technical help for every account after go-live, not just the biggest ones.

Technical help for every account after go-live, not just the biggest ones.

No integration left broken

Every account’s integrations are watched, whatever its size.

Every account’s integrations are watched, whatever its size.

Upgrades done before deadlines

Customers move off retiring versions with time to spare.

Answers in minutes

Technical questions get answered from your docs, without waiting for an engineer.

Logged and reviewable

Every answer, fix and escalation is recorded for your team.

See the Solutions Engineer on your product

Tell us where your customers get stuck technically, and we’ll show you how a Kulu agent handles it.

See the Solutions Engineer on your product

Tell us where your customers get stuck technically, and we’ll show you how a Kulu agent handles it.