Contracts Support Records

Retrieval metadata

feature_group: "Contracts"
record_count: 6
approx_page_tokens: 4072
recommended_chunking: one Knowledge Record section per vector chunk

Feature group overview

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

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

Knowledge Record: Contracts / Contracts visible in a table view (Name, Customer, Notes, Date Created, Auto ...

record_id: LFS-contracts-contracts-visible-in-a-table-view-name-customer-notes-date-created-auto

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting
• quickbooks_sync
• permissions_visibility

Sample user utterances

• How do I set up Contracts visible in a table view (Name, Customer, Notes, Date Created, Auto in Lexul?
• When should we use Contracts visible in a table view (Name, Customer, Notes, Date Created, Auto?
• Why is Contracts visible in a table view (Name, Customer, Notes, Date Created, Auto not working or not showing?
• Can Lexul handle Contracts visible in a table view (Name, Customer, Notes, Date Created, Auto for our workflow?

Entities to extract

• user_role
• workspace
• feature_area
• customer_name
• asset_name
• billing_contact
• contract_name
• service_date_window
• price_rule

Approved answer basis

Contracts group, recreate, duplicate, and organize related work orders over time. Use it when customers have recurring service, preventative maintenance, multi-site work, or seasonal services. Before giving exact setup steps, confirm: Is the contract for recurring dates, duplicated work across assets, or general service organization. Then explain the recommended configuration, test with a sample record, and note this guardrail: Use individual start/end dates and frequencies for services when seasonality or different cadences matter.

Configure when

customers have recurring service, preventative maintenance, multi-site work, or seasonal services.

Ask before answering

Is the contract for recurring dates, duplicated work across assets, or general service organization?

Dependencies

• Customer records
• asset/service-location structure
• user permissions
• customer/asset records
• services/items
• contract terms and pricing

Role workflow

Office/admin configures contract; dispatcher schedules generated work; technicians complete work; accounting bills.

Permissions and visibility

Confirm the user role before giving edit instructions. Provide view-only guidance to technicians unless the customer has granted edit rights.

Known limits and guardrails

Use individual start/end dates and frequencies for services when seasonality or different cadences matter.

Escalation rule

Escalate custom contract automation, unusual billing terms, or requested roadmap commitments.

Source URLs

• https://help.lexul.com/en/articles/7888462-contract-management

Default response pattern

For questions about Contracts visible in a table view (Name, Customer, Notes, Date Created, Auto ..., 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: Contracts / Custom fields

record_id: LFS-contracts-custom-fields

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting

Sample user utterances

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

Entities to extract

• user_role
• workspace
• feature_area
• customer_name
• asset_name
• billing_contact
• contract_name
• service_date_window
• price_rule

Approved answer basis

Contract custom fields capture information specific to the agreement or service plan. Use it when contracts require renewal terms, billing notes, service tiers, seasonal windows, or account-specific rules. Before giving exact setup steps, confirm: What contract data must be visible during setup, dispatch, or billing. Then explain the recommended configuration, test with a sample record, and note this guardrail: Keep contract fields focused on agreement-level data; use work order fields for job-specific details.

Configure when

contracts require renewal terms, billing notes, service tiers, seasonal windows, or account-specific rules.

Ask before answering

What contract data must be visible during setup, dispatch, or billing?

Dependencies

• Customer records
• asset/service-location structure
• user permissions
• customer/asset records
• services/items
• contract terms and pricing

Role workflow

Office/admin configures contract; dispatcher schedules generated work; technicians complete work; accounting bills.

Permissions and visibility

Confirm the user role before giving edit instructions. Provide view-only guidance to technicians unless the customer has granted edit rights.

Known limits and guardrails

Keep contract fields focused on agreement-level data; use work order fields for job-specific details.

Escalation rule

Escalate custom contract automation, unusual billing terms, or requested roadmap commitments.

Source URLs

• https://www.lexul.com/custom-fields/
• https://help.lexul.com/en/articles/7888462-contract-management

Default response pattern

For questions about Custom fields, 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: Contracts / Contract Assets

record_id: LFS-contracts-contract-assets

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting
• quickbooks_sync

Sample user utterances

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

Entities to extract

• user_role
• workspace
• feature_area
• customer_name
• asset_name
• billing_contact
• contract_name
• service_date_window
• price_rule

Approved answer basis

Contract assets define the locations/equipment covered by a contract. Use it when a customer has multiple stores, properties, equipment units, or service sites under one agreement. Before giving exact setup steps, confirm: Which assets are covered, and should each asset receive its own duplicated/recurring work order. Then explain the recommended configuration, test with a sample record, and note this guardrail: Confirm asset list before recurring/duplicate work orders are generated to avoid extra or missing jobs.

Configure when

a customer has multiple stores, properties, equipment units, or service sites under one agreement.

Ask before answering

Which assets are covered, and should each asset receive its own duplicated/recurring work order?

Dependencies

• Customer records
• asset/service-location structure
• user permissions
• customer/asset records
• services/items
• contract terms and pricing

Role workflow

Office/admin configures contract; dispatcher schedules generated work; technicians complete work; accounting bills.

Permissions and visibility

Confirm the user role before giving edit instructions. Provide view-only guidance to technicians unless the customer has granted edit rights.

Known limits and guardrails

Confirm asset list before recurring/duplicate work orders are generated to avoid extra or missing jobs.

Escalation rule

Escalate custom contract automation, unusual billing terms, or requested roadmap commitments.

Source URLs

• https://help.lexul.com/en/articles/7888462-contract-management

Default response pattern

For questions about Contract Assets, 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: Contracts / Work orders

record_id: LFS-contracts-work-orders

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting

Sample user utterances

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

Entities to extract

• user_role
• workspace
• feature_area
• customer_name
• asset_name
• billing_contact
• contract_name
• service_date_window
• price_rule

Approved answer basis

Contract work orders are the operational jobs created/organized under the contract. Use it when contracted work should be searchable, filtered, duplicated, or recurring from the agreement. Before giving exact setup steps, confirm: Should work orders be one-time, duplicated per asset, recurring by interval, or grouped by service type. Then explain the recommended configuration, test with a sample record, and note this guardrail: Use contract filtering on the dashboard to find related work.

Configure when

contracted work should be searchable, filtered, duplicated, or recurring from the agreement.

Ask before answering

Should work orders be one-time, duplicated per asset, recurring by interval, or grouped by service type?

Dependencies

• Customer records
• asset/service-location structure
• user permissions
• customer/asset records
• services/items
• contract terms and pricing

Role workflow

Office/admin configures contract; dispatcher schedules generated work; technicians complete work; accounting bills.

Permissions and visibility

Confirm the user role before giving edit instructions. Provide view-only guidance to technicians unless the customer has granted edit rights.

Known limits and guardrails

Use contract filtering on the dashboard to find related work.

Escalation rule

Escalate custom contract automation, unusual billing terms, or requested roadmap commitments.

Source URLs

• https://help.lexul.com/en/articles/7888462-contract-management

Default response pattern

For questions about Work orders, 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: Contracts / Documents

record_id: LFS-contracts-documents

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting
• permissions_visibility

Sample user utterances

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

Entities to extract

• user_role
• workspace
• feature_area
• customer_name
• asset_name
• billing_contact
• contract_name
• service_date_window
• price_rule

Approved answer basis

Contract documents store agreement-level files and make them available on related work orders. Use it when contract terms, scope exhibits, service procedures, or account instructions should follow every contract job. Before giving exact setup steps, confirm: Who should view the contract document: techs, office staff, or only admins. Then explain the recommended configuration, test with a sample record, and note this guardrail: Documents inherited from contracts show on work orders based on permissions and are edited at the contract.

Configure when

contract terms, scope exhibits, service procedures, or account instructions should follow every contract job.

Ask before answering

Who should view the contract document: techs, office staff, or only admins?

Dependencies

• Customer records
• asset/service-location structure
• user permissions
• customer/asset records
• services/items
• contract terms and pricing

Role workflow

Office/admin configures contract; dispatcher schedules generated work; technicians complete work; accounting bills.

Permissions and visibility

Confirm document visibility level. Technicians may view assigned/inherited documents but should not manage sensitive account-level files unless allowed.

Known limits and guardrails

Documents inherited from contracts show on work orders based on permissions and are edited at the contract.

Escalation rule

Escalate custom contract automation, unusual billing terms, or requested roadmap commitments.

Source URLs

• https://help.lexul.com/en/articles/7229123-document-management
• https://www.lexul.com/work-order-documents/

Default response pattern

For questions about Documents, 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: Contracts / Price Rules

record_id: LFS-contracts-price-rules

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting

Sample user utterances

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

Entities to extract

• user_role
• workspace
• feature_area
• customer_name
• asset_name
• billing_contact
• contract_name
• service_date_window
• price_rule

Approved answer basis

Price rules/contract-specific rates document how pricing changes for a specific customer or contract. Use it when contract customers have negotiated rates, service-specific rates, or recurring pricing rules. Before giving exact setup steps, confirm: Are rates customer-specific, contract-specific, item-specific, or time/material based. Then explain the recommended configuration, test with a sample record, and note this guardrail: If not covered in public KB, escalate setup details and avoid promising line-item behavior not documented.

Configure when

contract customers have negotiated rates, service-specific rates, or recurring pricing rules.

Ask before answering

Are rates customer-specific, contract-specific, item-specific, or time/material based?

Dependencies

• Customer records
• asset/service-location structure
• user permissions
• customer/asset records
• services/items
• contract terms and pricing

Role workflow

Office/admin configures contract; dispatcher schedules generated work; technicians complete work; accounting bills.

Permissions and visibility

Confirm the user role before giving edit instructions. Provide view-only guidance to technicians unless the customer has granted edit rights.

Known limits and guardrails

If not covered in public KB, escalate setup details and avoid promising line-item behavior not documented.

Escalation rule

Escalate custom contract automation, unusual billing terms, or requested roadmap commitments.

Source URLs

• https://help.lexul.com/en/articles/7888462-contract-management
• https://www.lexul.com/how-lexul-quickbooks-combine-to-deliver-true-erp-level-functionality-for-field-service-businesses/

Default response pattern

For questions about Price Rules, 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.