Customer requests
Record customers and connect their feedback to Issues and Projects.
Customer requests connect feedback from the organizations you serve to the work they asked for. Create a customer, then attach a Request to an existing Issue or Project, or create an Issue with the Request attached.
Configure customer requests
A workspace owner or admin can turn on Customer requests in workspace settings. Every workspace member can then create and edit customers and Requests. People who only have access to a shared Source or folder cannot use customer requests.
Settings also control the default Team for new Issues, customer statuses and tiers, the revenue currency, and whether revenue appears annually or monthly. Revenue is stored as an annual amount. Only owners and admins can change these settings. Agents cannot change them.
Statuses and tiers have colour dots. Edit their colour, name and description directly in each row. Select + to create an option; Enter saves and Escape cancels. Drag status or tier rows to reorder them; the other rows slide aside as you drag. The integration sections show Coming soon.
Turning the feature off hides customer pages, navigation, Request sections and actions. It also prevents customer reads and writes through agents and downloads. It keeps customers and Requests, so turning it back on brings them back. Existing Issue and Project Activity remains visible as history.
Create and open customers
Open More → Customers from the workspace sidebar. Select the icon-only create button in the Customers header, whose tooltip is Create new customer. You can also use Create customer or Open customer in the command menu. Create a customer with a name and any details you know: domain, owner, status, tier, annual revenue and employee count. A domain can belong to only one customer in a workspace, including archived and recently deleted customers.
The Customers view has two columns: a customer list on the left and the selected customer’s page on the right. Search by name or domain, use Filter to narrow the list and Display to choose its ordering and visible properties. Switch between Customers, Archived and Recently deleted tabs. The customer detail pane has no breadcrumb. Select a customer to edit its properties and see its readable Requests grouped by Issue or Project. Use Copy URL to share the page with another workspace member. The URL stays the same after a rename. Ordering, filters and display properties are kept for your customer list; search is temporary.
The customer header shows its domain, when its record was created and the latest readable Request. Four summary cards show Requests and important feedback, open Issues and Triage, Projects in progress, and completed targets with the latest completion date when it can be determined. If historical completion dates are unavailable, the card keeps the completed count and says so. Multiple Requests on the same Issue or Project count as one target. All counts and dates use only work you can read. Properties remain editable in the label-and-value grid. Use the icon buttons for Copy URL and Download CSV; Copy slug is in the customer’s ⋯ menu.
Add a customer logo
Click the avatar in the create dialog or on an editable customer page and choose Upload image, or drop an image onto it. PNG, WebP, JPG and SVG files up to 1 MB are accepted. Transparency is preserved. SVG files are cleaned and converted to PNG for safe display. Choose Remove logo from the avatar menu to return to the coloured initial.
On a customer page with a domain, choose Use logo from [domain] in the avatar menu. Integrity reads the site’s icons directly over HTTPS. If it cannot find a usable icon, upload an image instead. ICO icons need to be replaced with a PNG, WebP, JPG or SVG upload. Only people who can edit the customer can change its logo.
If the customer was created but its logo could not be confirmed, select Save logo to retry. This keeps the same customer. If another member changed it, review the refreshed properties before retrying.
Workspace members who can read the customer can see its logo. Archived customers keep their logo; restore the customer before changing it. Logos remain visible in Recently deleted during the 30-day recovery window and are removed after permanent deletion.
Add and manage Requests
On a customer page, select New request, or Add customer request in the command menu, to open the inline composer above the Requests list. Enter the feedback, requester, source link and optional important marker. Adds to starts with a new Issue: choose a Team and edit the title, which is prefilled from the first line of your request. The hint shows Triage when that Team's Triage is on, or Backlog when it is off. You can instead link an existing Issue or Project. Select Add request to save or Cancel to close the composer.
Requests are grouped under their Issue or Project, using the same status and property presentation as the work tables, with a request count for this customer. Each Request shows its requester, important marker, source and relative time. Long feedback is clamped to two lines; select Show more to read it and Show less to collapse it.
From an Issue, use the Customers section. From a Project, choose Add customer request in its menu or the command menu. The Project's Customer requests tab appears once it has a readable Request.
A Request contains feedback text and can include a requester name, a source link and an important marker. You can edit it, mark it important or delete it after confirmation. Request text does not support mentions or slash commands. Adding and removing a Request records Activity on its Issue or Project.
A Request follows access to its target. If you cannot read an Issue or Project, its Requests do not appear in customer pages, counts, CSV downloads or agent results. There is no hidden Request count. A private Team's Issue remains private to people with access.
Archive, delete and restore
Archive a customer when you want to keep its record and Requests but remove it from the active list and pickers. Its page remains available with an archived banner. Restore it to return it to active work.
Delete a customer to move it to Recently deleted for 30 days. Its Requests disappear from ordinary pages during that time. Restore the customer from Recently deleted to bring them back. After permanent deletion, its domain can be used again, but the old customer URL is never reused. Deleting an Issue or Project also hides its Requests; restoring the target brings them back.
Download and export
Select Download CSV on a customer page to download all the Requests you can read for that customer. The download uses your current browser session and access, including for archived customers. Agents cannot download the CSV. Search and display columns on the page do not limit the download.
Workspace owners and admins can request a Standard Workspace Export. It includes active and archived customers, their logos and Requests whose target is within the exporter's access. Only owners can request Full, which includes private Team Issues and their Requests together. Recently deleted customers, their Requests and Requests on deleted Issues or Projects are excluded. Customer data is omitted while customer requests are off; disabling the feature does not delete it.
Work through an agent
The five customer tools are available in Integrity AI. MCP availability comes later, after deployed qualification.
In Integrity AI, an agent can find customers, read their Requests, create and edit customers, link feedback to existing Issues or Projects, and mark Requests important using your access. Customer deletion requires confirmation. To create new work through an agent, create the Issue first, then attach the Request.
What comes later
Support-tool integrations, automatic customer matching, synced customer attributes, customer filters in saved Issue or Project views, and customer-request notifications are not available yet. The disabled integration sections in settings show Coming soon. For now, record feedback by hand or through an agent.