Skip to content
Docs menu

Customer requests in Venom Tasks

Link Support conversations, People companies and Funnel deals to issues and projects as customer requests, see who asked and what it is worth, and sort, filter and chart issues by that demand.

View .md

A customer request says "this customer asked for this". It links an issue (or a project) to a record you already have: a Support conversation, a People company or a Funnel deal. Tasks keeps no customer list of its own. The conversation, company or deal stays where it is, and the request only points at it, with an optional quote of what the customer said.

From the requests, every issue gets its demand: how many requests, from how many customers, and the value of the open and won deals behind them.

Add a request

  • On an issue: the Customer requests section under the description, or Add → Customer request in the issue's menu. Search for a conversation (by subject, customer or #number), a company or a deal, pick it, and add a quote if you like. The section is hidden while an issue has no requests.
  • On a project: the Customer requests section on the project page, under Resources.
  • From Support: Add to issue next to Create issue under the conversation's title (or the MCP tool support_issue_link). Pick the issue and add a quote. Create issue makes the conversation the new issue's first request on its own.

Linking a conversation that has no issue yet also links the issue on the conversation, as Create issue does, so the customer still gets the "we fixed it" draft when the issue is completed. A conversation already linked to another issue keeps that link and is counted as a request on both.

Linking the same record to the same issue again changes its quote instead of adding a second request. Removing a request leaves the conversation, company or deal as it was.

Who counts as a customer

A request counts as one customer:

  1. the People company it belongs to: the company itself, the deal's company, or the company of the person shared with the org behind the Support customer (else a company with the same name as the Support customer's company);
  2. otherwise the Support customer;
  3. otherwise the request on its own.

So a conversation from someone at Acme, the Acme company and an Acme deal on the same issue are three requests from one customer.

Revenue is the sum of the deals, open or won (never lost or archived), that a request points at or that belong to a requesting company. Each deal counts once per issue. When the deals use different currencies, the sum shows without a currency symbol and is only a rough guide.

Who sees what

Each request shows only to people who may open the record it points at, by that product's own rules:

Record Who sees it
Support conversation Everyone in the org, except a conversation assigned to a private team: only that team's members and the org's owners and admins
People company Everyone with People access
Funnel deal An org deal: everyone with Funnel access. A team deal: that team's members, its owner and its creator

The counts follow the same rules, so demand never tells you about a record you can't open. The section says how many other requests there are that you can't see. A team key (no member behind it) sees the Support requests only.

Lists, boards and Insights

  • Display → Customers shows a chip with the customer count and the deal value on each row and card (on by default; hover it for the request count).
  • Filter → Customer requests: requested by customers, 3 or more, 10 or more, or no requests.
  • Ordering: Customer requests, Customers or Customer revenue, most first. Customers break ties by requests, and revenue by customers. Issues without requests come last.
  • The advanced filter and filter take the fields requests and customers (numbers: is, isNot, in, notIn, lt, lte, gt, gte, isEmpty, isNotEmpty) and revenue (in major units such as dollars: lt, lte, gt, gte, isEmpty, isNotEmpty). No requests is empty. orderBy takes requests, customers and revenue.
  • Insights has the Customer requests measure (the sum of requests on the issues) and the Customer slice and segment (the customers who asked; an issue with three customers counts once for each).

API and MCP

Endpoint MCP tool What
GET /tasks/api/issues/{id}/requests tasks_request_list {requests, hidden, demand}: the requests you may see, oldest first, how many others there are, and the demand
POST /tasks/api/issues/{id}/requests tasks_request_create one of conversation (number, #12 or id), company (id or exact name) or deal (id), and an optional quote (up to 2000 characters). 201 with {request, created: true, demand}; linking it again answers 200 with created: false
GET, POST /tasks/api/projects/{id}/requests tasks_projectrequest_list, tasks_projectrequest_create the same for a project
PATCH /tasks/api/requests/{id} tasks_request_update {quote}
DELETE /tasks/api/requests/{id} tasks_request_delete removes the request
GET /tasks/api/requests/sources?q=&kind=&limit= tasks_customer_search what you may link: {results: [{source, id, title, detail}]}; kind is support, company or deal (comma-separated), limit 1 to 20 per kind
POST /api/v1/support/conversations/{conversation}/requests support_issue_link Support's Add to issue: {issue, quote?}

Every issue in GET /tasks/api/issues and GET /tasks/api/issues/{id} carries demand: {requests, customers, revenueMinor, currency}, or null without requests, as the caller sees it. Adding, changing or removing a request is an issue (or project) change on the live feed, so open lists refresh it.