Inspections Support Records

Retrieval metadata

feature_group: "Inspections"
record_count: 3
approx_page_tokens: 1909
recommended_chunking: one Knowledge Record section per vector chunk

Feature group overview

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

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

Knowledge Record: Inspections / Inspection Lists

record_id: LFS-inspections-inspection-lists

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting

Sample user utterances

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

Entities to extract

• user_role
• workspace
• feature_area
• inspection_list
• question_type
• service_name

Approved answer basis

Inspection lists are pre-service checklists/surveys assigned to work orders. Use it when technicians must collect standardized jobsite information, photos, asset data, or customer-required checks before work. Before giving exact setup steps, confirm: What inspection list should be used, and is it tied to the type of work being performed. Then explain the recommended configuration, test with a sample record, and note this guardrail: Pre-service inspection lists are managed in Inspections; service-specific questions drive post-service behavior.

Configure when

technicians must collect standardized jobsite information, photos, asset data, or customer-required checks before work.

Ask before answering

What inspection list should be used, and is it tied to the type of work being performed?

Dependencies

• inspection lists
• questions
• service/work order type mapping

Role workflow

Admin builds inspection; technician answers questions; office reviews exceptions and photos.

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

Pre-service inspection lists are managed in Inspections; service-specific questions drive post-service behavior.

Escalation rule

Escalate when the user reports unexpected system behavior, requests a workflow not documented in sources, or needs custom development.

Source URLs

• https://help.lexul.com/en/articles/6749373-pre-post-service-inspections-office
• https://www.lexul.com/field-service-software/

Default response pattern

For questions about Inspection Lists, 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: Inspections / Inspection Questions

record_id: LFS-inspections-inspection-questions

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting

Sample user utterances

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

Entities to extract

• user_role
• workspace
• feature_area
• inspection_list
• question_type
• service_name

Approved answer basis

Inspection questions define the exact data the technician must collect. Use it when quality, safety, compliance, asset data, or sales opportunity questions must be asked consistently. Before giving exact setup steps, confirm: What answer type is needed: text, number, list, photo, yes/no, or required note. Then explain the recommended configuration, test with a sample record, and note this guardrail: Keep questions concise; too many required questions can slow technician adoption.

Configure when

quality, safety, compliance, asset data, or sales opportunity questions must be asked consistently.

Ask before answering

What answer type is needed: text, number, list, photo, yes/no, or required note?

Dependencies

• inspection lists
• questions
• service/work order type mapping

Role workflow

Admin builds inspection; technician answers questions; office reviews exceptions and photos.

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 questions concise; too many required questions can slow technician adoption.

Escalation rule

Escalate when the user reports unexpected system behavior, requests a workflow not documented in sources, or needs custom development.

Source URLs

• https://help.lexul.com/en/articles/6749373-pre-post-service-inspections-office
• https://www.lexul.com/field-service-software/

Default response pattern

For questions about Inspection Questions, 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: Inspections / Services

record_id: LFS-inspections-services

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting

Sample user utterances

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

Entities to extract

• user_role
• workspace
• feature_area
• inspection_list
• question_type
• service_name

Approved answer basis

Services can trigger post-service inspection questions based on what was performed. Use it when completion checks should change depending on the service selected on the work order. Before giving exact setup steps, confirm: Which service should cause which questions to appear. Then explain the recommended configuration, test with a sample record, and note this guardrail: For service-specific post inspections to populate, the related service must be added to the work order.

Configure when

completion checks should change depending on the service selected on the work order.

Ask before answering

Which service should cause which questions to appear?

Dependencies

• inspection lists
• questions
• service/work order type mapping

Role workflow

Admin builds inspection; technician answers questions; office reviews exceptions and photos.

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

For service-specific post inspections to populate, the related service must be added to the work order.

Escalation rule

Escalate when the user reports unexpected system behavior, requests a workflow not documented in sources, or needs custom development.

Source URLs

• https://help.lexul.com/en/articles/6749373-pre-post-service-inspections-office
• https://www.lexul.com/field-service-software/

Default response pattern

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