# Deal and ticket forms > New opportunity and new support ticket work like Quick Entry — a fixed core, blocks opened by the template, a quick panel from any page, sector presets and assignment rules. The **new opportunity** and **new support ticket** forms work like [Quick Entry](/guides/quick-entry): template tabs on top, a **core** that stays the same in every template, and **blocks** below that open with the template or wait as chips. The template brings the type, starting stage and close window for a deal, and the ticket type, priority, resolution time, category and assignment for a ticket. Sales reps only see what the job needs; the summary on the right shows what will be created before you save. The forms adapt to every sector: [13 sector presets](#presets) bring the Quick Entry, Opportunity and Support templates together, along with lists and extra fields when needed. ## New opportunity {#opp} **+ New Opportunity** on the opportunity list, **+ New sales opportunity** on the board, **+ Project** on a company page, or **+ New → Opportunity** on phones. | Core | What you enter | |---|---| | **Company** | Type the company name; a registered company is picked, otherwise it's created as a **prospect**. If a similarly named company exists the form warns you — pick it from the list or choose **Create a new company anyway**. Opened from a company page, the company is preselected. | | **Name · type · owner** | The name is optional (type and year are shown when empty). The type comes from the template; the owner defaults to you. | | **Estimated value · expected close** | Value and currency; the close date is calculated from the template's window (e.g. 120 days) and changes with the **1 month · 3 months · 6 months · 1 year** chips. | The line under the title shows the stage the deal opens in. With stage rules on (BANT, required steps) a deal always opens in the first stage; with them off the template's starting stage is used. [Pipeline](/concepts/pipeline) | Block | What it writes | |---|---| | **Product and quantity** | Product (added to the list if new), monthly potential (in the product's unit), line / application. The value is quantity × price × 12. | | **Price and terms** | Unit price and payment terms — recorded in offer history. | | **Forecast** | Forecast category, probability, next step date. | | **Source and competitor** | Lead source, competitor / current supplier. | | **Decision makers** | The company's contacts as chips; the selected ones are linked to the deal. | | **BANT** | Budget, authority, need, timing (with stage rules on). | | **Trial plan** | Planned date, line, note — opens a trial (with the Trials module). | | **First tasks** | The template's task list arrives checked: *Send sample · +5 days*. Unchecked tasks aren't created; you can add new ones. | | **Status label · Need and note** | Status label (when labels are used) and a note about the customer's need. | | **Extra fields** | The deal's [custom fields](/concepts/custom-fields) — the template chooses which ones appear. | | **Files** | Quote, data sheet, photo. | | **Custom objects** | Every [custom object](/guides/custom-objects) that can link to deals is a block (e.g. *Production line*): pick one of the company's records. | **Edit opportunity** opens the same form: blocks with values are open, and the first-tasks and trial blocks aren't shown when editing. Closing a block in the form doesn't clear the stored value — only the blocks you send change. ## New support ticket {#ticket} **Support tickets → + New support ticket**, **Open a support ticket** / **+ Ticket** on a company page, **+ Ticket** on a deal page, or **+ New → Support ticket** on phones. | Core | What you enter | |---|---| | **Ticket type** | One line under the title: **Ticket type · Quality complaint · change**. The type comes from the template; *change* changes it for this ticket only and shows a **different from template** badge. | | **Company · contact** | The company may be unregistered — the ticket keeps the company name. For a registered company its contacts come as chips; **+ Another contact** for name, email and phone. | | **Subject · what happened** | The subject is required; the description is free text. | | **Priority · assignee · category** | Priority (Low · Normal · High · Urgent) with the **resolution target** below it. The assignee is *By template* or picked by hand. A category is only asked when a category list is defined. | The **resolution target** is the priority's standard time (Settings → Stages → *Support ticket resolution target*; by default Urgent 4 h, High 24 h, Normal 72 h, Low 7 days). A template can carry its own time (e.g. *Breakdown report* · Urgent · 8 h); if the rep picks a different priority than the template's, the priority's standard time applies. **Assignment** follows the template's rule; picking an assignee by hand skips the rule: | Rule | Who gets the ticket | |---|---| | **Team: Quality** | The user in that department with the **fewest open tickets**. The summary shows why (*Quality team · fewest open tickets*). | | **Account owner** | The company's owner (not assigned for an unregistered company or when there's no owner). | | **Creator** | The person filling in the form. | | **User** | The person chosen in the template. | | **No assignment** | Nobody; shown as unassigned in the support list. | | Block | What it writes | |---|---| | **Product and batch** | Product (from registered products) and lot / batch number. | | **Order** | One of the company's recent orders. | | **Related deal** | One of the company's projects. | | **Channel** | Phone, email, visit, WhatsApp, web, mobile. | | **Site visit** | Visit date and note — creates a *Site visit* task for the assignee. | | **Extra fields** | The ticket's custom fields (e.g. *Machine serial no*, *Defective quantity*). | | **File / photo** | Photo of the defect, report. | | **Custom objects** | Custom objects that can link to tickets. | A chip block can open on a condition: *priority is high or urgent* (e.g. site visit), *existing customer*, *the company has an open deal*. On the ticket page extra fields and relationships have their own cards; **Edit** opens the same form. ## Quick panel {#quick-panel} Any new-deal link on any page (**+ New Opportunity**, **+ Project** …) or new-ticket link (**+ New support ticket**, **+ Ticket** …) opens a short panel from the right (from the bottom on phones): template chips, company and 4–5 fields. - **Opportunity:** company, deal name, estimated value, expected close, owner. - **Support ticket:** company, contact, subject, priority, what happened. The panel applies the template's open blocks and defaults (first tasks included) by itself; if one of the template's required blocks stays empty the panel warns you — use **Go to the full form** to fill it in. **Go to the full form** carries what you've typed to the full page. `Esc` closes the panel; `Ctrl` / `⌘`-click opens the link as the full form in a new tab. ## Templates {#templates} Admins edit templates under **Settings → Forms**. The tabs on top choose the form: **Quick Entry · Opportunity · Support** — the editor is the same as for [Quick Entry templates](/guides/quick-entry#templates): drag blocks between **Open in form · Waiting as a chip · Off**, set name, required, condition, visible fields and default values in the card settings, and the preview on the right redraws the form on every change. | Template setting | Opportunity | Support ticket | |---|---|---| | **Name · icon** | ✓ | ✓ | | **Type** | Opportunity type | Ticket type | | **Stage · time** | Starting stage, expected close (days) | Priority, resolution time (hours; empty = the priority's time) | | **Other** | — | Category, assignment rule, channel | | **Department** | ✓ | ✓ | | **Default template** | ✓ | ✓ | A template with a **Department** opens first for users in that department (e.g. the *Quality* department starts with *Quality complaint*); otherwise the default template. When editing a deal, the template it was opened with is used. On first use the templates follow the installation's sector. Older opportunity templates from Settings → Templates (field defaults and first tasks included) are converted to form templates and added to the list. ## Lists {#lists} The form's drop-down lists are managed from cards on the same page: add items, remove them with ×, drag to reorder and **Save**. **Reset to default** returns to the original list. - **Opportunity types** (Opportunity tab) — the type options on the deal form. - **Ticket types** and **Categories** (Support tab) — at least one type is required; with an empty category list the form doesn't ask for a category. Older values that are no longer on a list are kept on records and offered when editing. ## Sector presets {#presets} **Settings → Forms → Sector presets** shows the sectors in three groups: general, manufacturing and services. Click a card (**Preview and edit**): that sector's **three forms** — Quick Entry, Opportunity and Support templates — open in the same editor; switch between forms with the buttons on top. **Nothing is saved before you install.** | Sector | Opportunity templates | Support templates | |---|---|---| | **General** | New business, Upsell, Renewal | Complaint, Technical support, Question / information, Return | | **Chemicals / manufacturing** | New product approval, Supplier switch, Extra volume | Quality complaint, Application / process support, Document request (TDS / SDS / CoA), Sample request | | **Distributor / wholesale** | New dealer / customer, Annual agreement, Campaign | Missing / damaged delivery, Return request, Invoice / price difference, Stock / lead time question | | **Software / SaaS** | New customer, Expansion, Renewal, Pilot / POC | Bug report, Usage question, Feature request, Account / billing | | **Services / consulting** | New project, Additional work, Retainer renewal | Change request, Complaint, Information request | | **Automotive supplier** | RFQ — new part, Annual price agreement, Engineering change | 8D quality complaint, Delivery / lead time, PPAP / document request | | **Food / beverage** | New listing, Private label, Annual agreement | Food safety complaint, Cold chain / delivery, Return, Document request | | **Construction materials** | Site project, Tender, Dealer agreement | Site technical support, Quality complaint, Shipment / lead time | | **Machinery / equipment** | New machine, Service agreement, Spare parts | Breakdown report, Maintenance request, Spare part request | | **Logistics** | New route, Warehousing, Annual tender | Damage / loss, Delay, Documents / customs, Invoice dispute | | **Medical / healthcare** | Public tender, Direct purchase, Device + consumables | Device failure, Adverse event / product complaint, Training request | | **Education** | Corporate training, Institution licence, Renewal | Access problem, Certificate request, Training complaint | | **Real estate / development** | Residential sale, Commercial / office, Rental | Snagging / handover, Fault / maintenance, Title deed / documents | Template names appear in Turkish in the product. Each sector's Quick Entry templates are in the [Quick Entry › Sector presets](/guides/quick-entry#presets) table. With **Also install lists and extra fields** checked (the default) the sector's opportunity types, ticket types, categories and topics are installed too, and missing [custom fields](/concepts/custom-fields) are added — e.g. *Part no*, *Annual volume*, *SOP date*, *Defective quantity* for automotive; *Machine serial no*, *Machine status*, *Under warranty* for machinery; *Origin*, *Destination*, *Transport type*, *Bill of lading / waybill no* for logistics. Existing fields are left untouched. - **Install all (n templates)** — your edited set replaces the existing templates in all three forms. - **Add this template to my templates** — only the open template is added to that form's existing templates (numbered if the name exists). :::tip The older single-page forms remain at `?klasik=1`: `/opportunities/new?klasik=1`, `/tickets/new?klasik=1`. Linking from elsewhere: `?tpl=