Topic

Technical Support

2 posts about Technical Support. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

Resend
Welcoming Michael Vaz, our new Customer Success Engineer
Resend introduces Michael Vaz as a new Customer Success Engineer based in Portugal, with experience in systems administration, networking, support engineering, cybersecurity, SaaS video, and email-related products. He began in technology by installing, configuring, and maintaining email servers, then developed broader experience at Sophos and Loom, including exposure to SaaS and startup scaling. At Resend, he says he wants to help unblock people, ensure systems work well for customers, and contribute to a product he finds easy to start with and capable of growing with users’ needs. His preferred tools include log platforms such as Datadog, which he describes as a source of truth when diagnosing failures, while his background also shapes a people-centered approach to support and problem-solving.

Cursor
How technical support at Cursor uses Cursor
Cursor’s technical support team treats customer investigations as research problems, using a single session to combine code, logs, team knowledge, and past conversations. Engineers typically start in Ask Mode, use semantic search across a locally indexed codebase and documentation, and group related repositories with multi-root workspaces. MCP servers bring customer data, Datadog logs and traces, Slack and support history, runbooks, account details, and ticketing context into those investigations; Linear MCP turns evidence into escalations, while a Slack-mentioned cloud agent can open documentation pull requests. Slash commands, Rules, Skills, and parallel subagents automate repeated work, including failure analysis, known-issue searches, ticket writing, and customer-response drafting. The team reports that more than 75% of support interactions run through Cursor, with stated throughput gains of 5–10x and estimated productivity improvements of up to an order of magnitude.

The best engineering reads, once a week.

Topic

2 posts about Technical Support. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Resend
Welcoming Michael Vaz, our new Customer Success Engineer
Resend introduces Michael Vaz as a new Customer Success Engineer based in Portugal, with experience in systems administration, networking, support engineering, cybersecurity, SaaS video, and email-related products. He began in technology by installing, configuring, and maintaining email servers, then developed broader experience at Sophos and Loom, including exposure to SaaS and startup scaling. At Resend, he says he wants to help unblock people, ensure systems work well for customers, and contribute to a product he finds easy to start with and capable of growing with users’ needs. His preferred tools include log platforms such as Datadog, which he describes as a source of truth when diagnosing failures, while his background also shapes a people-centered approach to support and problem-solving.

Cursor
How technical support at Cursor uses Cursor
Cursor’s technical support team treats customer investigations as research problems, using a single session to combine code, logs, team knowledge, and past conversations. Engineers typically start in Ask Mode, use semantic search across a locally indexed codebase and documentation, and group related repositories with multi-root workspaces. MCP servers bring customer data, Datadog logs and traces, Slack and support history, runbooks, account details, and ticketing context into those investigations; Linear MCP turns evidence into escalations, while a Slack-mentioned cloud agent can open documentation pull requests. Slash commands, Rules, Skills, and parallel subagents automate repeated work, including failure analysis, known-issue searches, ticket writing, and customer-response drafting. The team reports that more than 75% of support interactions run through Cursor, with stated throughput gains of 5–10x and estimated productivity improvements of up to an order of magnitude.

The best engineering reads, once a week.