Support, routed like code

Customer support that lives in your issue tracker

Issued turns support form submissions into Linear or GitHub issues and threads your replies back to customers over email. Built for indie devs and small teams who'd rather fix the bug than manage a helpdesk — with every ticket arriving ready for AI coding agents.

live in ~5 min · from $10/mo
Connects with Linear GitHub
your app · support widget
Subject
Export fails on Safari
Description
Clicking “Export CSV” shows a 500 error. Works fine in Chrome.
Hidden metadata
email: sarah@acme.devplan: prov2.4.1safari 17
Send report
issue created
linear · acme / bugs
ISS-142High

Export fails on Safari

bugsupportcustomer-request
reporter  sarah@acme.dev · pro
version   2.4.1 · safari 17
page      /dashboard/exports
opened by issued · just now
comment ↔ email
customer inbox
You · via issue comment[ISS-142]

Found it — Safari's blob handling. Fixed in v2.4.2, rolling out now. Can you confirm?

Sarah replies→ synced to issue

Works now. Thank you!

no portal, no login — just email
No helpdesk softwareNo context switchingNo per-seat pricingNo customer portalsNo copy-pasting tickets into issuesNo unread support inbox
No helpdesk softwareNo context switchingNo per-seat pricingNo customer portalsNo copy-pasting tickets into issuesNo unread support inbox
01How it works

Form in. Issue out. Replies threaded.

01

Embed the form

Drop the widget into your site or app — JavaScript, React, Vue, iOS, Android, Flutter, or a plain iframe. Configure every field: visible, hidden, required, or pre-filled with user data your customer never has to type.

<script src="https://issued.dev/widget/issued.js"></script>
<script>
  Issued.init({
    projectId: "acme-app",
    fields: {
      email:      { visible: false, value: user.email },
      appVersion: { visible: false, value: "2.4.1" }
    }
  });
</script>
02

An issue opens with full context

Every submission becomes a Linear or GitHub issue — title, description, reporter, plan, app version, URL, attachments. It lands on the right team with your default labels, status, and priority already set. No triage inbox in between.

issued → linear · acme / bugs
subjectissue title
hidden fieldsreporter · pro · v2.4.1
screenshot.pngattachment
project defaultsteam · labels · priority
ISS-142Highbugsupport

Export fails on Safari

filed on the Frontend team — nothing touched by hand
03

Reply without leaving the issue

Comment on the issue and Issued emails it to the customer from your project’s reply address. Prefix a comment with (ignore) to keep it internal. You never open another tool.

linear · ISS-142 · comments
You commented → sarah@acme.dev

Found it — Safari's blob handling. Fixed in v2.4.2, rolling out now. Can you confirm?

You commented internal only

(ignore) repro video in #eng-bugs — Safari 17 only.

the comment is the reply — no other tool opened
04

The thread stays in sync

When the customer replies to that email, their response lands back on the issue as a comment. Close the issue when you ship the fix — the whole conversation lives next to the code that caused it.

ISS-142 · activity
sarah@acme.dev replied via email2m

Works now. Thank you!

→ added to the issue as a comment
You closed ISS-142 as Donenow
the whole thread lives next to the fix
02The part nobody else does

Tickets your coding agents can actually fix

A support email in a helpdesk is a dead end for an AI agent. An issue in your tracker — with structured metadata, repro context, and the customer thread attached — is a work item. Point Claude Code, Cursor, or Devin at it and let them ship the fix.

  • Hidden form fields arrive as structured metadata — plan, version, platform, URL
  • Repro context and attachments land on the issue, not in an inbox
  • The customer thread stays attached, so agents see the whole story
~/acme-app
$claude "fix ISS-142: Export fails on Safari"
Reading issue ISS-142 from Linear
Context: pro plan · v2.4.1 · safari 17 · /dashboard/exports
Reproduced: blob download rejected by Safari
Patch applied · 14 tests passing
PR #318 opened: fix Safari CSV export encoding
$
issued · ai triage · incoming
New submission

Export button greyed out on iPad

Summary

iPad Safari: export disabled after login. Same blob-handling path as the desktop Safari CSV bug.

Suggested
label: buglabel: exportspriority: Highcategory: defect
Likely duplicate of ISS-142grouped

Export fails on Safari · 3 reports linked

iPadOS version missingclarifying reply drafted
agent handoff context compiled · ready to pipe
03The upgrade

Tickets that triage themselves

On the AI Triage plan, every submission is read the moment it lands — summarized, labeled, prioritized, and checked against your recent reports. You open the ticket to fix it, not to figure out what it is.

  • A summary plus suggested labels, category, and priority on every submission
  • Duplicates and related reports grouped before you see them
  • Vague reports get a clarifying reply drafted automatically
  • Agent handoff context compiled per issue — ready to paste or pipe
$20/mo · everything in Core included
//Watch it run

Ninety seconds, end to end

issued.dev/demo
04What's in the box

Everything a helpdesk does, minus the helpdesk

01

Two-way email sync

Comments become customer emails; replies become issue comments. Ticket IDs keep threads matched, and (ignore) keeps internal notes internal.

02

Fields you control

Every field visible, hidden, required, or pre-filled. Pass user IDs, plans, versions, error logs — and map form data to labels, assignees, and priorities.

03

Linear-native

Submissions auto-create Linear Customers and attach as Requests. Installs as a bot — zero billable seats in your workspace.

04

Locked down

Domain whitelisting, bundle ID validation, rate limiting, encrypted tokens. GDPR-compliant with automatic 30-day data deletion.

05

Your workspace stays private

Customers only ever see the form and their email thread — never your repo, roadmap, or workspace.

06

Every platform

JavaScript, React, Vue, React Native, iOS, Android, Flutter, iframe — the same field model and callbacks everywhere.

07

AI Triage

Upgrade and every submission arrives summarized, labeled, prioritized, and deduplicated — with clarifying replies drafted and agent handoff context compiled.

05Who it's for

Built for teams where the devs answer support

SOLO

Indie developers

You are the support team. Issued means support happens in the one tool you already have open — and your $10/mo replaces a $200/mo helpdesk.

SMALL TEAM

Small product teams

Everyone with access to your tracker can handle support. No new seats, no new logins, no “who owns the support inbox” standup item.

AI-FIRST

Agent-driven teams

Your agents already work from issues. Issued makes customer problems arrive as issues — triaged, deduplicated, and ready to assign.

06Pricing

Two plans. No seats. No submission caps.

Configure everything free. Activate a plan when you're ready for real submissions to flow.

Core

Route customer support into your developer workflow.

$10.00/mo
  • Unlimited projects & submissions
  • Linear / GitHub issue creation
  • Embedded forms on every platform
  • Custom fields, metadata & attachments
  • Two-way email sync
  • Webhooks & analytics
  • Security controls
Recommended

AI Triage

Every customer issue prepared for humans and coding agents.

$20.00/mo
  • Everything in Core
  • AI-generated issue summaries
  • Suggested labels, category & priority
  • Duplicate / related issue grouping
  • Missing-info detection
  • Clarification reply drafts
  • Agent handoff context
07FAQ

Questions, answered

$ issued init --provider linear

Ship support like you ship code

Connect your tracker, embed the form, and close your first customer-reported issue today — without opening a helpdesk tab ever again.

Core $10/mo · AI Triage $20/mo · cancel anytime