Customer requests, pipelines and stages

Organization requests are gathered in the "Customer requests" tab of the "Organizations" section: responses and offers on listings, tender bids, leasing requests, conversations and procurements taken on, and requests added manually. The filter above the feed picks the organization. The organization owner and managers see all requests, other employees — their own and those without an owner.

Request feed

Filter by pipeline, stage, state, type, request owner, participant and custom field value, with the "Without an owner", "Overdue" and "Without next contact" marks; search by client, contact and subject. Under the request owner, the due date of the next contact — the nearest open task of the request — and the date of the last touch are shown. "Export" saves a file with the requests of the current filter. "Without next contact" shows open requests only.

Saved views

"Saved views" in the feed filter bar set a ready filter at once: "My new", "Without manager", "Without next contact", "Overdue".

  • "Save view" records the current search and filter under your own name, and the view appears in the same menu.
  • "Rename view" and "Delete view" are available for a chosen view of your own; a deletion can be undone in the notification.
  • The chosen view stays in the page address: the link opens the same feed. Changing the search or the filter clears the chosen view.

Request card

A click on a request opens its card. Stage, request owner and due date are saved on selection, the amount — on leaving the field. "Take it on" moves a new request into work, "Close" — with the outcome "Deal took place" or "Deal did not take place", "Return to work" reopens a closed one. "Create a proposal" builds a commercial proposal from the request, "Print" saves its printable form.

Touches and next contact

The "Touches" feed of the request card gathers changes of stage, state and request owner, notes and meeting outcomes; notes are not visible to the client. "Add a note" records a note in the feed.

  • "Meeting" creates a calendar event linked to the request: the meeting appears under "Meetings" of the card and in the participants' calendar. "Meeting outcome" under a meeting records its outcome in the feed.
  • "Next contact" creates a task for the request owner: the name is what to do, the due date is when. Open tasks of the request are shown under "Next contact", checking one off closes the task.
  • A linked task or event shows the request name, which opens the request card.

"Files" holds the request files from the organization drive: "Add a file" picks a drive file, "Remove" detaches it from the request, and the file stays on the drive. A file deleted from the drive disappears from the request too.

"Participants" lists the counterparties of the request: the client, a designer, a contractor and others. "Edit participants" adds a counterparty from your counterparties and sets its role and contact person; one participant carries the "Client" mark. The organization's custom fields are filled in the card, and "Save" records their values.

Deal money

The "Deal money" block of a request card in the Deals module sums up the money of the request. "Paid by client" is the paid share of accepted commercial proposals, and "Client balance due" is what the client still owes on them. "Planned profit" is the gross profit of the request specification. With the Finance module and the finance view permission, the block also shows "Paid to suppliers" and "Due to suppliers" — settled and planned payments of the request, with paid and due amounts per counterparty below — and "Actual profit" — income minus expenses with the request as their accounting object.

The Deals module

Adding requests manually, participants, custom fields, pipelines, the stage board and processing rules are the Deals module. Without the module, "New request" offers to turn it on.

How to add a request

  1. Press "New request".
  2. Choose the channel: call, email, meeting, website, external tender or other.
  3. Pick the client from your counterparties or press "New client" — it is added to your counterparties together with the request.
  4. Describe the subject, set the amount, due date, request owner and pipeline; "Site address" is picked from suggestions, "Add a file" attaches files from the organization drive.
  5. Save the request.

If the client already has an open request with a similar subject, the card of the new one warns about it, and "Open the similar one" opens it.

Request settings

The organization owner and managers see the "Request settings" button. The "Pipelines" tab holds pipelines and stages, participant roles and custom fields, and the "Rules", "Queues", "Reply templates" and "Working hours" tabs hold request processing. The first pipeline, "Sales", comes with a starter set of stages.

  • "Add a pipeline" creates a pipeline with the starter set of stages; the pencil renames it, the bin removes a pipeline without requests, the last one cannot be removed.
  • "Add a stage" — a name and a state: new, in progress or closed; a closing stage gets an outcome.
  • Stages are reordered by dragging; a stage with requests and the last stage of its state cannot be removed.
  • A request moved to another pipeline in its card goes to the first stage of that pipeline.
  • "Add a role" creates a participant role; a role held by a request participant cannot be removed.
  • "Add a field" — a name and a type: text, number, yes/no, date or a list with options. A removed field and a removed list option disappear from all requests.

Processing rules

A rule performs actions on a request by itself when its event happens and the request matches its conditions. "Add rule" in the "Rules" tab sets a name, an "Event", "Conditions" and "Actions"; the "Enabled" switch stops a rule without deleting it.

  • Events: a new request, a stage change, no touch within the period, a proposal viewed or accepted, an invoice paid. "No touch within the period" takes a "Period without a touch, min".
  • Conditions compare the stage, type, channel, subject category, region, amount, a custom field and the organization working hours. A rule without conditions matches any request.
  • Actions: assign the request owner — a member or a queue, reply with a template in the request conversation, create a task, move to a stage, notify a member. A task and a notification without a chosen member go to the request owner.
  • Rules are checked in list order, and dragging changes the order. Every matching rule fires, and the first matching rule with an assignment sets the request owner.
  • Each rule action is recorded in the request "Touches" with the rule name, and one that could not be performed — with the reason.

In the "Queues" tab, "Add queue" gathers the members a rule distributes requests among: "Round-robin" — in turn, "Least loaded" — to the member with the fewest open requests.

In the "Reply templates" tab, "Add template" sets the name and the reply text; the "Insert" buttons put the client, the subject and the request owner into the text. The "Working hours" tab sets working hours by day of the week, and "Save" records them; the "Working hours" condition tells requests within working hours from those outside them.

Reply with a template

"Reply with a template" in the request card, next to the conversation link, opens the list of templates. The chosen template with the request data filled in goes into the conversation input field: the text can be edited before sending.

Stage board

The "View" switch → "Board" shows the requests of the chosen pipeline in stage columns. Press and hold a request card and move it to another column — the request moves to that stage; moving it to a closing stage closes it with the stage outcome.

Request map

"View" → "Map" shows requests with a site address as points under the same filter as the list; nearby points merge into a circle with the number of requests, and zooming in separates them. A click on a point opens the request card. The site address is set when the request is added and in its card.

Handing over work

The organization owner and managers hand over an employee's work to another employee: the organization "Employees" tab → the employee card menu → "Hand over work" → "To". Open requests where the employee is the owner or the supply manager, the employee's clients and open tasks move over; closed requests and completed tasks stay with the employee. Removing an employee from the organization offers the same choice of whom to hand their work over to.

Was this article helpful?

Did not find the answer to your question?

Create a request