Customers, branches and assignment

In Vuntus, every request belongs to a branch and a customer. The owner and managers keep customer records on the Customers page; branches and auto-assignment rules are in Settings › Branches & assignment. Team members only see the records of the branches and customers assigned to them.

This page covers customer records, branches, the rules that route a request to the right person, and manual assignment. Customers and Settings in the sidebar are visible to the owner and managers only.

Adding a customer

1. 01
   Open the Customers page

   Go to Customers in the sidebar. The list shows each customer’s request count, quotes won and lost, and last activity.

2. 02
   Open the new customer form

   Select Add customer. Only the Legal name is required; you can add the rest now or later.

3. 03
   Enter the details

   The form has four sections: Company (Legal name, Account code, Tax ID (VKN) / National ID (TCKN), Tax office), Contact (Contact person, Email, Phone), Address (Address, Province, District) and Commercial (Payment terms, Quote document language, Notes). Fields marked “On quote” are printed in the buyer section of the quote document.

4. 04
   Save

   Select Save, or press Ctrl/⌘+Enter in any field. The customer is added to the scope of the manager who added it and of the owners.

• Account code is the customer’s account code in your ERP and must be unique within the company.
• Payment terms are suggested on this customer’s quotes instead of the company default.
• If Quote document language is left blank, the company default language is used.
• Notes are visible to your team only; they are not printed on the quote document.
• For a customer with no tax or contact details, only the legal name is printed as the buyer on the quote document.

Importing a customer list from CSV

Import CSV opens the Import customer list window. You can get the headers with Download sample template, then choose a file or paste the contents. English or Turkish headers are accepted; the separator can be a semicolon or a comma, and up to 2,000 rows are accepted per file.

1. Select Preview. Each row shows its result: new, will be updated, or no change.
2. An existing customer is matched by account code first, otherwise by tax ID (VKN/TCKN), and updated; if none is found, a new customer is created. Empty cells do not erase existing details.
3. If the preview is clean, select Import. If any row has an error, no customers are written; errors are listed with their row numbers.

Archiving a customer

Archive on the customer page means the customer can no longer be selected for new requests and is hidden from the list by default. Past requests and quotes stay as they are. Select Restore to bring the customer back at any time.

What is on the customer page?

Clicking a customer opens Customer 360: record details, the number of requests, quotes won and lost, and the request history. Each request shows its branch, channel, status and quote or outcome amount. Amounts are shown net (excl. VAT) first, with the amount incl. VAT next to it. Use Edit details to update the record.

Some details are customer-specific and are entered on other screens:

Branches

Every document and request belongs to a branch. In Settings › Branches & assignment, type the branch name on the Branches card and select Add branch. A new branch is added to the scope of the owners and of the manager who added it. The same tab also shows a short customer summary with a Manage customers link.

Auto-assignment rules

A new request is assigned automatically to the assignee of the first matching rule. With no rules, requests wait unassigned in the queue. The New rule section has four fields:

Branch

A specific branch, or Any branch.

Customer

A specific customer, or Any customer.

Assignee

The team member the request is assigned to.

Priority

A whole number from 0 to 1000. Within a level, the higher one is tried first.

Rules are tried top to bottom: rules with both branch and customer first, then single-field rules, then general ones. A request is assigned only to an active member whose scope covers it; a rule for a member who has been removed does not run and shows “Member is not active” in the list. Remove a rule with the delete button on its row and confirm with Delete.

Assigning a request by hand

• One request: on the request page, choose an Assignee and Due date on the Assignee & due date card and select Assign; later, Update or Remove. Only active members whose branch and customer scope covers this request are listed.
• Several requests: select requests in the request queue, choose Select assignee and Due date, then Assign. Requests outside the person’s scope are skipped, and the number skipped is shown.
• Only the owner and managers can assign. A closed request needs no new assignment.

Who sees which customers?

Everyone sees only the records of the branches and customers assigned to them, and this rule is enforced in the database; how scope is chosen and how it works: Team and roles.

What these screens do not have

• Renaming or deleting a branch.
• A screen to change a member’s branch and customer scope after the invitation.
• Syncing customer records with an ERP or CRM; the customer list comes in by CSV.
• Sending emails, reminders or notifications to customers.