Sales Support Records

Retrieval metadata

feature_group: "Sales"
record_count: 4
approx_page_tokens: 2968
recommended_chunking: one Knowledge Record section per vector chunk

Feature group overview

This page contains chatbot training records for Sales sub-features. Retrieve one ### Knowledge Record: chunk at a time when possible.

This section contains chatbot training records for Sales sub-features.

Knowledge Record: Sales / Deals

record_id: LFS-sales-deals

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync

Sample user utterances

How do I set up Deals in Lexul?
When should we use Deals?
Why is Deals not working or not showing?
Can Lexul handle Deals for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
customer_name
asset_name
billing_contact

Sales deals track prospects/opportunities before they become quoted or operational work. Use it when users need a pipeline for possible jobs, follow-ups, and conversion to quotes/work orders. Before giving exact setup steps, confirm: What deal stage is this in, and is there a customer/prospect already selected. Then explain the recommended configuration, test with a sample record, and note this guardrail: Create deal stages before adding deals so AI can guide users through a repeatable pipeline.

Configure when

users need a pipeline for possible jobs, follow-ups, and conversion to quotes/work orders.

Ask before answering

What deal stage is this in, and is there a customer/prospect already selected?

Dependencies

Customer records
asset/service-location structure
user permissions
QuickBooks version confirmed
integration settings checked
source-of-truth rules defined

Role workflow

Sales/office creates quote or deal; manager reviews; accounting converts, invoices, or syncs.

Permissions and visibility

Restrict quote, invoice, and sync actions to office/sales/accounting roles.

Known limits and guardrails

Create deal stages before adding deals so AI can guide users through a repeatable pipeline.

Escalation rule

Escalate custom quote/invoice formatting, missing sales records, or unsupported conversion workflows.

Source URLs

https://help.lexul.com/en/articles/13452343-deal-tracking-in-lexul

Default response pattern

For questions about Deals, first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Sales / Quotes, quotes visible in a table view (Date Created, Quote Number, Status, C...

record_id: LFS-sales-quotes-quotes-visible-in-a-table-view-date-created-quote-number-status-c

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
permissions_visibility

Sample user utterances

How do I set up Quotes, quotes visible in a table view (Date Created, Quote Number, Status, C in Lexul?
When should we use Quotes, quotes visible in a table view (Date Created, Quote Number, Status, C?
Why is Quotes, quotes visible in a table view (Date Created, Quote Number, Status, C not working or not showing?
Can Lexul handle Quotes, quotes visible in a table view (Date Created, Quote Number, Status, C for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
customer_name
asset_name
billing_contact

Approved answer basis

Quotes capture estimated services/parts and customer-facing pricing before work starts. Use it when users need customer approval, internal cost review, or a quote that can later copy to a work order. Before giving exact setup steps, confirm: Is the quote internal-only or customer-facing? What expiration date/status should apply. Then explain the recommended configuration, test with a sample record, and note this guardrail: Only customer quotes can be copied to a work order in the Deal workflow.

Configure when

users need customer approval, internal cost review, or a quote that can later copy to a work order.

Ask before answering

Is the quote internal-only or customer-facing? What expiration date/status should apply?

Dependencies

Customer records
asset/service-location structure
user permissions
QuickBooks version confirmed
integration settings checked
source-of-truth rules defined

Role workflow

Sales/office creates quote or deal; manager reviews; accounting converts, invoices, or syncs.

Permissions and visibility

Restrict quote, invoice, and sync actions to office/sales/accounting roles.

Known limits and guardrails

Only customer quotes can be copied to a work order in the Deal workflow.

Escalation rule

Escalate custom quote/invoice formatting, missing sales records, or unsupported conversion workflows.

Source URLs

Default response pattern

For questions about Quotes, quotes visible in a table view (Date Created, Quote Number, Status, C..., first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Sales / Invoices, invoices visible in a table view (Date Created, Invoices Number, Cu...

record_id: LFS-sales-invoices-invoices-visible-in-a-table-view-date-created-invoices-number-cu

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
permissions_visibility

Sample user utterances

How do I set up Invoices, invoices visible in a table view (Date Created, Invoices Number, Cu in Lexul?
When should we use Invoices, invoices visible in a table view (Date Created, Invoices Number, Cu?
Why is Invoices, invoices visible in a table view (Date Created, Invoices Number, Cu not working or not showing?
Can Lexul handle Invoices, invoices visible in a table view (Date Created, Invoices Number, Cu for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
customer_name
asset_name
billing_contact

Approved answer basis

Invoices convert completed work, parts, services, time, and notes into billable records. Use it when work is complete and office/accounting needs to bill or sync to QuickBooks. Before giving exact setup steps, confirm: Should this invoice be sent/synced now, or held for summary invoicing. Then explain the recommended configuration, test with a sample record, and note this guardrail: Invoices already sent or synced to QuickBooks cannot be used for Summary Invoicing.

Configure when

work is complete and office/accounting needs to bill or sync to QuickBooks.

Ask before answering

Should this invoice be sent/synced now, or held for summary invoicing?

Dependencies

Customer records
asset/service-location structure
user permissions
QuickBooks version confirmed
integration settings checked
source-of-truth rules defined

Role workflow

Sales/office creates quote or deal; manager reviews; accounting converts, invoices, or syncs.

Permissions and visibility

Restrict quote, invoice, and sync actions to office/sales/accounting roles.

Known limits and guardrails

Invoices already sent or synced to QuickBooks cannot be used for Summary Invoicing.

Escalation rule

Escalate if data is missing after sync, accounting source-of-truth is unclear, or the user asks for accounting treatment. Escalate custom quote/invoice formatting, missing sales records, or unsupported conversion workflows.

Source URLs

Default response pattern

For questions about Invoices, invoices visible in a table view (Date Created, Invoices Number, Cu..., first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Sales / Sales Orders, sales orders visible in a table view (Date Created, Number, Cus...

record_id: LFS-sales-sales-orders-sales-orders-visible-in-a-table-view-date-created-number-cus

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
permissions_visibility

Sample user utterances

How do I set up Sales Orders, sales orders visible in a table view (Date Created, Number, Cus in Lexul?
When should we use Sales Orders, sales orders visible in a table view (Date Created, Number, Cus?
Why is Sales Orders, sales orders visible in a table view (Date Created, Number, Cus not working or not showing?
Can Lexul handle Sales Orders, sales orders visible in a table view (Date Created, Number, Cus for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
customer_name
asset_name
billing_contact

Approved answer basis

Sales orders should be documented as the operational bridge between accepted sale and fulfillment when used. Use it when the customer needs a pre-work fulfillment/order step before a work order or invoice. Before giving exact setup steps, confirm: Is Sales Order part of their current Lexul workflow, or should the job proceed as quote-to-work-order. Then explain the recommended configuration, test with a sample record, and note this guardrail: No dedicated public KB article was found; document supported fields/actions internally and escalate uncertain behavior.

Configure when

the customer needs a pre-work fulfillment/order step before a work order or invoice.

Ask before answering

Is Sales Order part of their current Lexul workflow, or should the job proceed as quote-to-work-order?

Dependencies

Customer records
asset/service-location structure
user permissions
QuickBooks version confirmed
integration settings checked
source-of-truth rules defined

Role workflow

Sales/office creates quote or deal; manager reviews; accounting converts, invoices, or syncs.

Permissions and visibility

Restrict quote, invoice, and sync actions to office/sales/accounting roles.

Known limits and guardrails

No dedicated public KB article was found; document supported fields/actions internally and escalate uncertain behavior.

Escalation rule

Escalate custom quote/invoice formatting, missing sales records, or unsupported conversion workflows.

Source URLs

Default response pattern

For questions about Sales Orders, sales orders visible in a table view (Date Created, Number, Cus..., first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Sales Support Records

On this page