LawFlow Call Block Reference Guide

Call block

AI Conversation

ai_conversation

Runtime ready with required config

What this block does

Uses AI instructions and a selected input source to classify, summarise, cleanse or extract structured call information.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required
provider	`provider`	Check settings
model	`model`	Check settings
input_source	`input_source`	Check settings
save_target	`save_target`	Check settings
system_instruction	`system_instruction`	Check settings
user_instruction	`user_instruction`	Check settings
output_schema	`output_schema`	Check settings

Runtime behaviour

Uses AI instructions and a selected input source to classify, summarise, cleanse or extract structured call information.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 18942
Line 19055
Line 20013

Call block

API Lookup

api_lookup

Runtime ready

What this block does

Calls an external or internal API lookup and saves the configured result.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Request Method	`request_method`	No	GET
Endpoint URL	`endpoint_url`	No	text
Headers JSON	`headers_json`	No	json
Query Params JSON	`query_params_json`	No	json
Body JSON	`body_json`	No	json
Timeout Seconds	`timeout_seconds`	No	10
Response Mapping JSON	`response_mapping_json`	No	json
Save Target	`save_target`	No	master_call_record
Success Route Label	`success_route_label`	No	Success
Not Found Route Label	`not_found_route_label`	No	Not Found
Error Route Label	`error_route_label`	No	Error

Runtime behaviour

Calls an external or internal API lookup and saves the configured result.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 306 LAWFLOW_API_LOOKUP_SAVE_FIELDS
Line 307 LAWFLOW_API_LOOKUP_SAVE_FIELDS
Line 308 LAWFLOW_API_LOOKUP_SAVE_FIELDS

Call block

Ask Question

ask_question

Runtime ready

What this block does

Asks the caller a question, captures the spoken reply and saves it according to the block settings.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Prompt / instruction	`prompt`	No	textarea
Invalid / Retry Prompt	`invalid_prompt`	No	I want to make sure I understood correctly. Could you briefly explain that again?
Gather Fields JSON	`gather_fields`	No	{'caller_name': 0, 'callback_number': 1, 'reason_for_call': 1}
Save Target	`save_target`	No	master_call_record
Next Step	`next_step`	No	follow_connected_edge
Save Answer As	`save_policy`	No	runtime_only_not_committed
Memory Key	`memory_key`	No	last_ask_question

Runtime behaviour

Asks the caller a question, captures the spoken reply and saves it according to the block settings.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 624
Line 625
Line 797

Call block

Book Appointment

book_appointment

Runtime ready with required config

What this block does

Checks availability and books an appointment using the configured calendar strategy.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required
calendar_action	`calendar_action`	Check settings
appointment_type	`appointment_type`	Check settings
route_labels	`route_labels`	Check settings

Runtime behaviour

Checks availability and books an appointment using the configured calendar strategy.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 385 LAWFLOW_APPOINTMENT_REQUEST_CONFIRMATION_FIELDS_V1
Line 959
Line 960 LAWFLOW_BOOK_APPOINTMENT_SAVE_FI

Call block

Business Hours Check

business_hours_check

Runtime partial

What this block does

Checks whether the call is inside business hours and routes accordingly.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required
timezone	`timezone`	Check settings
open_time	`open_time`	Check settings
close_time	`close_time`	Check settings
open_days	`open_days`	Check settings

Runtime behaviour

Checks whether the call is inside business hours and routes accordingly.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Runtime source reference needs manual confirmation.

Call block

Call Contact

call_contact

Runtime ready with required config

What this block does

Calls or transfers to a configured or resolved contact.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Call Who / Number Source	`phone_source`	No	fixed_number
Number To Call	`fixed_number`	No	text
Caller ID Source	`caller_id_source`	No	client.lawflow_number
Fixed Caller ID	`fixed_caller_id`	No	text
Message To Play	`message_template`	No	Hello. This is LawFlow calling with an update.
Response Mode	`response_mode`	No	none
Option 1 Key	`accept_key`	No	1
Option 1 Route Label	`option_1_label`	No	Pressed 1
Option 2 Key	`reject_key`	No	2
Option 2 Route Label	`option_2_label`	No	Pressed 2
Option 3 Key	`option_3_key`	No	3
Option 3 Route Label	`option_3_label`	No	Pressed 3
Voice Save Target	`voice_save_target`	No	master_call_record.call_contact_response
Ring Timeout Seconds	`ring_timeout_seconds`	No	20
Next Step	`next_step`	No	follow_connected_edge
Route Mode	`route_mode`	No	route_label
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Calls or transfers to a configured or resolved contact.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 1186 LAWFLOW_TRANSFER_SAVE_FIELDS
Line 1207
Line 1219 LAWFLOW_RING_TEAM_BLOCK_V1

Call block

Call Recording Control

call_recording_control

Runtime ready

What this block does

Call Recording Control is a LawFlow call-flow block used inside the Call Flow Designer.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Recording Action	`recording_action`	No	start
Recording Track	`recording_track`	No	both
Recording Channels	`recording_channels`	No	mono
Recording Status Callback	`recording_status_callback_enabled`	No	true
Consent Notice	`consent_notice`	No	textarea
Play Consent Notice	`play_consent_notice`	No	false
Active Recording SID Source	`active_recording_sid_source`	No	master_call_record.call_recording_sid
Save Target	`save_target`	No	master_call_record
Next Step	`next_step`	No	follow_connected_edge
Success Route Label	`success_route_label`	No	Done
Error Route Label	`error_route_label`	No	Error

Runtime behaviour

Call Recording Control is a LawFlow call-flow block used inside the Call Flow Designer.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 291 LAWFLOW_CALL_RECORDING_CONTROL_ACTIONS
Line 292 LAWFLOW_CALL_RECORDING_CONTROL_ACTIONS
Line 1522 LAWFLOW_CALL_RECORDING_CONTROL_ACTIONS

Call block

Callback Request

callback_request

Runtime ready with required config

What this block does

Creates a callback request/action for staff follow-up.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Source Target	`source_target`	No	master_call_record
Caller Name Source	`caller_name_source`	No	caller_name
Caller Phone Source	`caller_phone_source`	No	caller_phone
Routing Mode Source	`routing_mode_source`	No	routing_mode
Requested Staff ID Source	`requested_staff_id_source`	No	requested_staff_id
Requested Staff Name Source	`requested_staff_name_source`	No	requested_staff_name
Requested Staff Name Raw Source	`requested_staff_name_raw_source`	No	requested_staff_name_raw
Department Source	`department_source`	No	department
Department ID Source	`department_id_source`	No	department_id
Matter Type Source	`matter_type_source`	No	matter_type
Urgency Level Source	`urgency_level_source`	No	urgency_level
Summary Source	`summary_source`	No	summary
Callback Ready Source	`callback_ready_source`	No	callback_ready
Fallback Department Source	`fallback_department_source`	No	fallback_department
Default Status	`default_status`	No	open
Default Priority	`default_priority`	No	normal
Create When Not Ready	`create_when_not_ready`	No	checkbox
Fallback Mode When Not Ready	`fallback_mode_when_not_ready`	No	front_office_clarification
Link To Master Call Record	`link_to_master_call_record`	No	True
Next Step	`next_step`	No	follow_connected_edge

Runtime behaviour

Creates a callback request/action for staff follow-up.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 333 LAWFLOW_AI_OPERATIONAL_SAVE_FIELDS
Line 1476 LAWFLOW_RETRY_SAVE_FIELDS
Line 1477 LAWFLOW_RETRY_SAVE_FIELDS

Call block

Cancel Booking

cancel_booking

Runtime ready with required config

What this block does

Finds and cancels an existing booking where the required booking details are available.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required
booking_lookup_mode	`booking_lookup_mode`	Check settings
save_target	`save_target`	Check settings
next_step	`next_step`	Check settings
route_labels	`route_labels`	Check settings

Runtime behaviour

Finds and cancels an existing booking where the required booking details are available.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 411 LAWFLOW_YES_NO_CHECK_SAVE_FIELDS
Line 412 LAWFLOW_CANCEL_BOOKING_FIELDS_V1
Line 1042 LAWFLOW_YES_NO_CHECK_SAVE_FIELDS

Call block

Cancel & Replace Booking

cancel_replace_booking

Inactive / not user-facing

What this block does

Cancel & Replace Booking is a LawFlow call-flow block used inside the Call Flow Designer.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required
existing_booking_lookup_mode	`existing_booking_lookup_mode`	Check settings
calendar_target_mode	`calendar_target_mode`	Check settings
appointment_type	`appointment_type`	Check settings
save_target	`save_target`	Check settings
next_step	`next_step`	Check settings
route_labels	`route_labels`	Check settings

Runtime behaviour

Cancel & Replace Booking is a LawFlow call-flow block used inside the Call Flow Designer.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Runtime source reference needs manual confirmation.

Call block

Check Calendar Now

check_calendar_now

Runtime ready with required config

What this block does

Check Calendar Now is a LawFlow call-flow block used inside the Call Flow Designer.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Staff Source	`staff_source`	No	master_call_record.matched_staff_id
Availability Window Minutes	`duration_minutes`	No	15
Timezone	`timezone`	No	Europe/London
Save Target	`save_target`	No	master_call_record
Next Step	`next_step`	No	follow_route_label
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Check Calendar Now is a LawFlow call-flow block used inside the Call Flow Designer.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 362 LAWFLOW_CHECK_CALENDAR_NOW_SAVE_FIELDS
Line 679 LAWFLOW_RESOLVE_STAFF_MEMBER_SAVE_FIELDS
Line 738 LAWFLOW_CHECK_CALENDAR_NOW_SAVE_FIELDS

Call block

Check Group Calendar

check_group_calendar

Runtime ready with required config

What this block does

Check Group Calendar is a LawFlow call-flow block used inside the Call Flow Designer.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Group Source	`group_source`	No	master_call_record.department
Fixed Group	`fixed_group`	No	text
Matter Type Source	`matter_type_source`	No	master_call_record.matter_type
Fixed Matter Type	`fixed_matter_type`	No	text
Appointment Request Source	`appointment_request_source`	No	master_call_record.appointment_requested_time_text
Blank Request Policy	`blank_request_policy`	No	needs_clarification
Duration Minutes	`duration_minutes`	No	30
Timezone	`timezone`	No	Europe/London
Eligible Staff Filter Mode	`eligible_staff_filter_mode`	No	department_or_matter_type
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Check Group Calendar is a LawFlow call-flow block used inside the Call Flow Designer.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 368 LAWFLOW_CHECK_CALENDAR_NOW_SAVE_FIELDS
Line 369 LAWFLOW_CHECK_CALENDAR_NOW_SAVE_FIELDS
Line 745 LAWFLOW_CHECK_CALENDAR_NOW_SAVE_FIELDS

Call block

Check Matter

check_matter

Runtime ready with required config

What this block does

Checks whether the caller’s issue matches an existing matter or should become a new matter.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Source Target	`source_target`	No	master_call_record
Confirmed Entity ID Source	`confirmed_entity_id_source`	No	confirmed_entity_id
Provisional Entity ID Source	`provisional_entity_id_source`	No	provisional_entity_id
Caller Phone Source	`caller_phone_source`	No	caller_phone
Department Source	`department_source`	No	department
Matter Type Source	`matter_type_source`	No	matter_type
Summary Source	`summary_source`	No	summary
Optional Matter Reference Source	`matter_reference_source`	No	select
Require Entity Or Phone	`require_entity_or_phone`	No	True
Next Step	`next_step`	No	follow_connected_edge
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Checks whether the caller’s issue matches an existing matter or should become a new matter.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 531 LAWFLOW_CHECK_MATTER_REFERENCE_SOURCES
Line 543 LAWFLOW_CHECK_MATTER_SAVE_FIELDS
Line 544 LAWFLOW_CHECK_MATTER_SAVE_FIELDS

Call block

Collect Information

collect_information

Runtime ready with required config

What this block does

Captures a specific caller detail, validates it where configured and saves it to the selected field.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Prompt	`prompt`	No	Please tell me your answer.
Capture Field	`capture_field`	No	caller_name
Save Target	`save_target`	No	master_call_record
Validation Type	`validation_type`	No	text
Required	`required`	No	True
Retry Count	`retry_count`	No	1
Missing Info Route Label	`missing_info_route_label`	No	Missing Info
Success Route Label	`success_route_label`	No	Success
Next Step	`next_step`	No	follow_connected_edge

Runtime behaviour

Captures a specific caller detail, validates it where configured and saves it to the selected field.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 471 LAWFLOW_COLLECT_INFORMATION_FIELDS
Line 2128 LAWFLOW_COLLECT_INFORMATION_FIELDS
Line 17558 LAWFLOW_COLLECT_INFORMATION_FIELDS

Call block

Confirm Details

confirm_details

Runtime ready

What this block does

Reads back collected information and captures the caller’s confirmation before continuing.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Input Source	`input_source`	No	master_call_record.last_caller_reply
Save Target	`save_target`	No	master_call_record
Validation JSON	`validation`	No	{'required': ['spoken_reply', 'confirmed'], 'allowed_values': {'confirmed': ['yes', 'no']}, 'min_confidence': 0.6}
Next Step	`next_step`	No	follow_connected_edge
Prompt / instruction	`prompt`	No	Hello, you have reached {{client_name}} reception. How may I help today?
Route Mode	`route_mode`	No	single_next
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Reads back collected information and captures the caller’s confirmation before continuing.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 17548 LAWFLOW_CONFIRM_DETAILS_TEMPLATE_SPEECH_V3
Line 19961 LAWFLOW_CONFIRM_DETAILS_PASS_TO_YES_NO_CHECK_V1
Line 23192 LAWFLOW_AI_RETRY_EXCLUDE_CONFIRM_DETAILS_V1

Call block

Conflict Check

conflict_check

Runtime ready

What this block does

Checks caller and opposing-party details against conflict and restricted-record data, then routes by outcome.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Input sources	`input_sources`	No	['master_call_record.caller_name', 'master_call_record.opposing_party_name']
LLM review	`llm_review`	No	yes
Model	`model`	No	gpt-5-mini
Default route	`default_route`	No	Needs Review
Route labels	`route_labels`	Check block settings

Runtime behaviour

Checks caller and opposing-party details against conflict and restricted-record data, then routes by outcome.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 6870
Line 6882
Line 6895

Call block

Create Matter

create_matter

Runtime ready with required config

What this block does

Creates a new matter using the collected call data.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Source Target	`source_target`	No	master_call_record
Confirmed Entity ID Source	`confirmed_entity_id_source`	No	confirmed_entity_id
Provisional Entity ID Source	`provisional_entity_id_source`	No	provisional_entity_id
Caller Name Source	`caller_name_source`	No	caller_name
Caller Phone Source	`caller_phone_source`	No	caller_phone
Department Source	`department_source`	No	department
Matter Type Source	`matter_type_source`	No	matter_type
Urgency Level Source	`urgency_level_source`	No	urgency_level
Summary Source	`summary_source`	No	summary
Default Status	`default_status`	No	active
Require Entity	`require_entity`	No	True
Require Matter Type	`require_matter_type`	No	True
Next Step	`next_step`	No	follow_connected_edge
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Creates a new matter using the collected call data.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 1509 LAWFLOW_CHECK_MATTER_SAVE_FIELDS
Line 1510 LAWFLOW_CHECK_MATTER_SAVE_FIELDS
Line 2371

Call block

Create Record

create_record

Runtime ready

What this block does

Creates or updates the master call record so later blocks have a persistent record to read and write.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
record_type	`record_type`	Check settings
save_target	`save_target`	Check settings

Runtime behaviour

Creates or updates the master call record so later blocks have a persistent record to read and write.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 14134 LAWFLOW_CREATE_RECORD_MASTER_CALL_RUNTIME_V4
Line 14186
Line 23227 LAWFLOW_CREATE_RECORD_AUTOADVANCE_SAVE_ORDER_V1

Call block

CRM Lookup

crm_lookup

Runtime partial

What this block does

Runs a configured lookup and saves the returned result into the selected target.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Lookup Mode	`lookup_mode`	No	custom_sql
SQL Query	`sql_query`	No	textarea
SQL Params JSON	`sql_params_json`	No	{'client_id': '{{client.id}}', 'caller_phone': '{{master_call_record.caller_phone}}', 'confirmed_entity_id': '{{master_call_record.confirmed_entity_id}}', 'provisional_entity_id': '{{master_call_record.provisional_entity_id}}'}
Result Format	`result_format`	No	text_summary
Row Template	`row_template`	No	{{id}} - {{display_name}}
Max Rows	`max_rows`	No	25
Save Target UDF	`save_target`	No	master_call_record.udf_text_1
Empty Result Behaviour	`empty_result_behavior`	No	save_empty_text
Error Behaviour	`error_behavior`	No	save_error_text
Next Step	`next_step`	No	follow_connected_edge
Error Route Label	`error_route_label`	No	Error
Silent Block	`silent`	No	true

Runtime behaviour

Runs a configured lookup and saves the returned result into the selected target.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 523 LAWFLOW_CRM_LOOKUP_SAVE_TARGETS
Line 14623 LAWFLOW_CRM_LOOKUP_RUNTIME_V1
Line 14696

Call block

Custom Condition (Legacy)

custom_condition

Runtime ready / legacy

What this block does

Legacy condition block that evaluates configured values or rules and routes accordingly.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Condition JSON	`condition_json`	No	{'field': 'master_call_record.department', 'operator': 'equals', 'value': 'criminal_defence'}
Route Mode	`route_mode`	No	yes_no
Unmatched Route	`unmatched_route`	No	No
Silent Block	`silent`	No	true
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Legacy condition block that evaluates configured values or rules and routes accordingly.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Runtime source reference needs manual confirmation.

Call block

Database Save

database_save

Runtime ready

What this block does

Saves configured values into the selected database target.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Save Target	`save_target`	No	master_call_record
Values JSON	`values_json`	No	json
Success Route Label	`success_route_label`	No	Saved
Error Route Label	`error_route_label`	No	Error

Runtime behaviour

Saves configured values into the selected database target.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 1447 LAWFLOW_API_LOOKUP_SAVE_FIELDS
Line 1448 LAWFLOW_API_LOOKUP_SAVE_FIELDS
Line 2526

Call block

Delay

delay

Runtime ready

What this block does

Waits for the configured duration before continuing.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Delay Seconds	`delay_seconds`	No	5
Delay Message	`delay_message`	No	textarea
Save Target	`save_target`	No	master_call_record
Success Route Label	`success_route_label`	No	Done
Error Route Label	`error_route_label`	No	Error

Runtime behaviour

Waits for the configured duration before continuing.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 313 LAWFLOW_API_LOOKUP_SAVE_FIELDS
Line 314 LAWFLOW_API_LOOKUP_SAVE_FIELDS
Line 315 LAWFLOW_API_LOOKUP_SAVE_FIELDS

Call block

End Call

end_call

Runtime ready

What this block does

Ends the call cleanly.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Block configuration	`config`	Depends on block	Open the block settings and complete the visible fields.

Runtime behaviour

Ends the call cleanly.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 864 LAWFLOW_CHECK_GROUP_CALENDAR_SAVE_FIELDS
Line 874 LAWFLOW_END_CALL_MATRIX_BLOCK_V1
Line 875

Call block

Entity Resolution

entity_resolution

Runtime ready with required config

What this block does

Attempts to match the caller to an existing entity using name, phone, email or entity type.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Source Target	`source_target`	No	master_call_record
Caller Name Source	`caller_name_source`	No	caller_name
Caller Phone Source	`caller_phone_source`	No	caller_phone
Caller Email Source	`caller_email_source`	No	caller_email
Entity Type Source	`entity_type_source`	No	entity_type
Classifier Confidence Source	`classifier_confidence_source`	No	classifier_confidence
Minimum Create Confidence	`minimum_create_confidence`	No	number
Allow Create When No Match	`allow_create_when_no_match`	No	checkbox
Require Name For Match	`require_name_for_match`	No	True
Require Phone For Match	`require_phone_for_match`	No	True
Require Entity Type For Create	`require_entity_type_for_create`	No	True
Next Step	`next_step`	No	follow_connected_edge
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Attempts to match the caller to an existing entity using name, phone, email or entity type.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 456 LAWFLOW_SEND_EMAIL_SAVE_FIELDS
Line 457 LAWFLOW_ENTITY_RESOLUTION_SAVE_FIELDS
Line 458 LAWFLOW_ENTITY_RESOLUTION_SAVE_FIELDS

Call block

Known Number?

existing_customer_check

Runtime ready with required config

What this block does

Checks whether the caller is known or new and routes the call.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Known Number Phone Source	`lookup_phone_source`	No	master_call_record.caller_phone
Caller Name Source	`lookup_name_source`	No	master_call_record.caller_name
Save Target	`save_target`	No	master_call_record
Save Fields	`save_fields`	No	['existing_customer_status', 'existing_customer_match_id', 'existing_customer_match_source', 'existing_customer_match_name', 'existing_customer_match_phone', 'existing_customer_confidence', 'existing_customer_notes']
Route Mode	`route_mode`	No	existing_customer_check
Known Number Route	`match_route_label`	No	Known Number
New Number Route	`no_match_route_label`	No	New Number
Needs Review Route	`review_route_label`	No	Needs Review
Error Route	`error_route_label`	No	Error
Silent Block	`silent`	No	true
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Checks whether the caller is known or new and routes the call.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 2042 LAWFLOW_EXISTING_CUSTOMER_CHECK_RUNTIME_V1
Line 20224
Line 20257

Call block

Fixed Voice Message

fixed_voice_message

Runtime ready

What this block does

Speaks a fixed message to the caller, then follows the connected next route.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
prompt	`prompt`	Check settings

Runtime behaviour

Speaks a fixed message to the caller, then follows the connected next route.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 18739 LAWFLOW_RUNTIME_MEMORY_INPUT_SOURCE_V1
Line 18767 LAWFLOW_ASK_QUESTION_OPTIONAL_SAVE_POLICY_V1
Line 20736 LAWFLOW_FIXED_VOICE_MESSAGE_SAY_THEN_REDIRECT_V1

Call block

Incoming Call

incoming_call

Runtime ready

What this block does

Starts the workflow when a call reaches LawFlow. It supplies the caller number, call SID and initial call context.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Caller Number	`from_number`	No	runtime
LawFlow Number	`to_number`	No	runtime
Client	`client`	No	runtime

Runtime behaviour

Starts the workflow when a call reaches LawFlow. It supplies the caller number, call SID and initial call context.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 9872
Line 16859
Line 9872

Call block

Intent Check

intent_check

Runtime ready with required config

What this block does

Classifies caller intent and routes by the configured intent labels.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
input_source	`input_source`	Check settings
route_labels	`route_labels`	Check settings

Runtime behaviour

Classifies caller intent and routes by the configured intent labels.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 18044 LAWFLOW_INTENT_CHECK_RUNTIME_V1
Line 20428 LAWFLOW_INTENT_CHECK_RUNTIME_V1
Line 20432

Call block

Linked Flow

linked_flow

Runtime ready

What this block does

Connects the current flow to another flow or off-page connector.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Linked Flow ID	`linked_flow_id`	No	text
Next Step	`next_step`	No	follow_connected_edge

Runtime behaviour

Connects the current flow to another flow or off-page connector.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 22442
Line 22448
Line 27473

Call block

Multiple Choice

multiple_choice

Runtime partial

What this block does

Routes the caller based on one of several configured choices.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Prompt / instruction	`prompt`	No	textarea
Choice Options JSON	`choice_options`	No	['Option 1', 'Option 2']
Input Source	`input_source`	No	master_call_record.last_caller_reply
Save Target	`save_target`	No	master_call_record
Route Mode	`route_mode`	No	multi_choice
Unmatched Route	`unmatched_route`	No	No
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Routes the caller based on one of several configured choices.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 20056 LAWFLOW_MULTIPLE_CHOICE_RUNTIME_V1
Line 20058 LAWFLOW_MULTIPLE_CHOICE_RUNTIME_V1
Line 23066

Call block

Record Voicemail

record_voicemail

Runtime ready

What this block does

Records voicemail and stores recording details for follow-up.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Recording Prompt	`prompt_text`	No	Please leave your message after the tone. Press # when finished.
Consent Notice	`consent_notice`	No	This message may be recorded and transcribed so the team can respond.
Play Consent Notice	`play_consent_notice`	No	true
Max Length Seconds	`max_length_seconds`	No	120
Finish On Key	`finish_on_key`	No	#
Timeout Seconds	`timeout_seconds`	No	5
Play Beep	`play_beep`	No	true
Trim Mode	`trim_mode`	No	trim-silence
Transcribe	`transcribe`	No	true
Save Target	`save_target`	No	master_call_record
Save Fields	`save_fields`	No	['voicemail_recording_sid', 'voicemail_recording_url', 'voicemail_recording_duration', 'voicemail_recording_status', 'voicemail_transcription_sid', 'voicemail_transcription_text', 'voicemail_transcription_status', 'voicemail_transcription_url', 'voicemail_recorded_at', 'voicemail_notes']
Next Step	`next_step`	No	follow_connected_edge
Success Route Label	`success_route_label`	No	Recorded
No Recording Route Label	`no_recording_route_label`	No	No Recording
Transcription Failed Route Label	`transcription_failed_route_label`	No	Transcription Failed
Error Route Label	`error_route_label`	No	Error

Runtime behaviour

Records voicemail and stores recording details for follow-up.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 278 LAWFLOW_RECORD_VOICEMAIL_SAVE_FIELDS
Line 1576 LAWFLOW_RECORD_VOICEMAIL_SAVE_FIELDS
Line 1606

Call block

Resolve Staff Member

resolve_staff_member

Runtime ready with required config

What this block does

Matches a requested staff member by name, department, role or contact details.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Staff Name Source	`input_source`	No	master_call_record.requested_staff_name
Department Clue Source	`department_source`	No	master_call_record.department
Minimum Confidence	`min_confidence`	No	0.75
Next Step	`next_step`	No	follow_route_label
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Matches a requested staff member by name, department, role or contact details.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 348 LAWFLOW_RESOLVE_STAFF_MEMBER_SAVE_FIELDS
Line 613 LAWFLOW_RESOLVE_STAFF_MEMBER_BLOCK_V1
Line 672 LAWFLOW_RESOLVE_STAFF_MEMBER_SAVE_FIELDS

Call block

Retry

retry

Runtime ready

What this block does

Retries a previous action or route according to retry settings.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Retry Target Mode	`retry_target_mode`	No	previous_node
Max Attempts	`max_attempts`	No	2
Retry Delay Seconds	`retry_delay_seconds`	No	3
Retry Message	`retry_message`	No	textarea
Save Target	`save_target`	No	master_call_record
Retry Route Label	`retry_route_label`	No	Retry
Failed Route Label	`failed_route_label`	No	Failed
Done Route Label	`done_route_label`	No	Done

Runtime behaviour

Retries a previous action or route according to retry settings.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 320 LAWFLOW_DELAY_SAVE_FIELDS
Line 321 LAWFLOW_DELAY_SAVE_FIELDS
Line 322 LAWFLOW_DELAY_SAVE_FIELDS

Call block

Ring Person

ring_person

Runtime ready with required config

What this block does

Attempts to ring one selected person.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Staff Source	`staff_source`	No	master_call_record.matched_staff_id
Fixed Staff ID	`fixed_staff_id`	No	number
Phone Source	`phone_source`	No	staff.primary_phone
Fixed Number	`fixed_number`	No	text
Caller Hold Message	`caller_hold_message`	No	Please hold while I try that person.
Staff Announcement	`staff_announcement_template`	No	LawFlow call for {{caller_phone}}. Press 1 to accept or 2 to reject.
Accept Key	`accept_key`	No	1
Reject Key	`reject_key`	No	2
Ring Timeout Seconds	`ring_timeout_seconds`	No	20
Caller ID Source	`caller_id_source`	No	client.lawflow_number
From Number Source	`from_number_source`	No	client.lawflow_number
Next Step	`next_step`	No	follow_connected_edge
Route Mode	`route_mode`	No	ring_person
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Attempts to ring one selected person.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 1153 LAWFLOW_CANCEL_BOOKING_SAVE_FIELDS
Line 1170
Line 1170

Call block

Ring Team

ring_team

Runtime ready with required config

What this block does

Attempts to ring a configured team or eligible group.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Team Source	`team_source`	No	master_call_record.department
Department Source	`department_source`	No	master_call_record.department
Fixed Department ID	`fixed_department_id`	No	number
Matter Type Source	`matter_type_source`	No	master_call_record.matter_type
Priority Mode	`priority_mode`	No	sequential
Max People To Try	`max_people_to_try`	No	3
Ring Timeout Seconds	`ring_timeout_seconds`	No	20
Caller Hold Message	`caller_hold_message`	No	Please hold while I try the team.
Staff Announcement	`staff_announcement_template`	No	LawFlow call for {{caller_phone}}. Press 1 to accept or 2 to reject.
Accept Key	`accept_key`	No	1
Reject Key	`reject_key`	No	2
Next Step	`next_step`	No	follow_connected_edge
Route Mode	`route_mode`	No	ring_team
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Attempts to ring a configured team or eligible group.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 1227 LAWFLOW_RING_TEAM_BLOCK_V1
Line 1244
Line 1244

Call block

Send Email

send_email

Runtime ready with required config

What this block does

Sends or prepares an email using configured recipient, subject and body template.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
To Email Source	`to_email_source`	No	fixed_email
Fixed To Email	`fixed_to_email`	No	text
CC Email Source	`cc_email_source`	No	none
Fixed CC Email	`fixed_cc_email`	No	text
BCC Email Source	`bcc_email_source`	No	none
Fixed BCC Email	`fixed_bcc_email`	No	text
Subject Template	`email_subject_template`	No	LawFlow call summary for {{caller_phone}}
Body Template	`email_body_template`	No	Call summary Caller: {{caller_name}} Phone: {{caller_phone}} Email: {{caller_email}} Reason: {{last_caller_reply}} Intent: {{intent_type}} Urgency: {{urgency_level}} Current outcome: {{current_node_label}} Call SID: {{call_sid}}
Include Audit Timeline	`include_audit_timeline`	No	checkbox
Next Step	`next_step`	No	follow_connected_edge
Route Mode	`route_mode`	No	send_email
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Sends or prepares an email using configured recipient, subject and body template.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 444 LAWFLOW_SEND_EMAIL_RUNTIME_FIELDS_V1
Line 445 LAWFLOW_SEND_EMAIL_RUNTIME_FIELDS_V1
Line 1317 LAWFLOW_TRANSFER_SAVE_FIELDS

Call block

Send SMS

send_sms

Runtime partial

What this block does

Sends an SMS using the configured number source, sender and message template.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required
to_number_source	`to_number_source`	Check settings
from_number_source	`from_number_source`	Check settings
message_template	`message_template`	Check settings

Runtime behaviour

Sends an SMS using the configured number source, sender and message template.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 13545
Line 13591
Line 13627

Call block

SMS Classifier

sms_classifier

Runtime ready with required config

What this block does

SMS Classifier is a LawFlow call-flow block used inside the Call Flow Designer.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Input Source	`input_source`	No	inbound_sms.body
Route Mode	`route_mode`	No	multi_output
Fallback Route	`fallback_route`	No	Unknown
Route Rules JSON	`route_rules`	No	{'Confirm': {'contains': ['yes', 'confirm', 'ok', 'fine', 'agreed']}, 'Cancel': {'contains': ['cancel', 'cancelled', "can't make it", 'cannot make it']}, 'Rearrange': {'contains': ['rearrange', 'reschedule', 'change time', 'another time']}, 'Human': {'contains': ['call me', 'person', 'solicitor', 'human']}, 'Unknown': {'fallback': True}}
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

SMS Classifier is a LawFlow call-flow block used inside the Call Flow Designer.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 24730
Line 24794 LAWFLOW_SMS_CLASSIFIER_SIMPLE_ROUTER_V1
Line 24862

Call block

SMS Received

sms_reply

Runtime ready

What this block does

Sends a simple SMS response/action and then follows the next route.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
To number source	`to_number_source`	No	master_call_record.caller_number
From number source	`from_number_source`	No	client.lawflow_number
Message text	`message_template`	No	Thanks. We have received your reply.
Next step	`next_step`	No	follow_connected_edge

Runtime behaviour

Sends a simple SMS response/action and then follows the next route.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 18621 LAWFLOW_SMS_REPLY_ROUTE_LABEL_FROM_CONTEXT_V1
Line 22276
Line 22333

Call block

Traffic Director

traffic_director

Runtime ready with required config

What this block does

Internal routing block intended to route saved workflow data to one of several labelled exits.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Input source	`input_source`	No	master_call_record.conflict_status
Traffic rules	`traffic_rules`	No	[{'label': 'Clear', 'operator': 'equals', 'value': 'clear'}, {'label': 'Possible Conflict', 'operator': 'equals', 'value': 'possible_conflict'}, {'label': 'Conflict', 'operator': 'equals', 'value': 'conflict'}, {'label': 'Restricted', 'operator': 'equals', 'value': 'restricted'}, {'label': 'Needs Review', 'operator': 'equals', 'value': 'needs_review'}, {'label': 'Missing Info', 'operator': 'equals', 'value': 'missing_info'}]
Default output	`default_route`	No	Needs Review
Route mode	`route_mode`	No	traffic
Route labels	`route_labels`	Check block settings

Runtime behaviour

Internal routing block intended to route saved workflow data to one of several labelled exits.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 13535
Line 13584
Line 20485 LAWFLOW_CONFLICT_CHECK_SAVE_STATUS_FOR_TRAFFIC_DIRECTOR_V1

Call block

Transfer Call

transfer_call

Runtime ready with required config

What this block does

Transfers the call to the configured number or destination.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Transfer Number Source	`transfer_number_source`	No	fixed_number
Fixed Transfer Number	`fixed_transfer_number`	No	text
Pre-transfer Message	`pre_transfer_message`	No	textarea
Transfer Timeout Seconds	`transfer_timeout_seconds`	No	25
Caller ID Source	`caller_id_source`	No	client.lawflow_number
From Number Source	`from_number_source`	No	client.lawflow_number
Continue After Transfer	`continue_after_transfer`	No	checkbox
Next Step	`next_step`	No	follow_connected_edge
Route Mode	`route_mode`	No	transfer_call
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Transfers the call to the configured number or destination.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 1260 LAWFLOW_TRANSFER_SAVE_FIELDS
Line 1273
Line 1273

Call block

Transfer Failed

transfer_failed

Runtime ready with required config

What this block does

Transfer Failed is a LawFlow call-flow block used inside the Call Flow Designer.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Failure Source	`failure_source`	No	latest_transfer_result
Save Target	`save_target`	No	master_call_record
Failure Reason Field	`failure_reason_field`	No	transfer_failure_reason
Failed Destination Field	`failed_destination_field`	No	transfer_failed_destination
Create Callback On Failure	`create_callback_on_failure`	No	checkbox
Callback Priority Source	`callback_priority_source`	No	master_call_record.urgency_level
Caller Message	`caller_message`	No	textarea
Next Step	`next_step`	No	follow_connected_edge
Route Mode	`route_mode`	No	transfer_failed
Route Labels JSON	`route_labels`	Check block settings

Runtime behaviour

Transfer Failed is a LawFlow call-flow block used inside the Call Flow Designer.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 437 LAWFLOW_TRANSFER_RUNTIME_FIELDS_V1
Line 1289 LAWFLOW_TRANSFER_SAVE_FIELDS
Line 1296

Call block

Voicemail

voicemail

Runtime ready

What this block does

Handles voicemail behaviour for the call flow.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Voicemail Prompt	`voicemail_prompt`	No	Please leave a message after the tone.
Save Target	`save_target`	No	master_call_record
Next Step	`next_step`	No	follow_connected_edge

Runtime behaviour

Handles voicemail behaviour for the call flow.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 278 LAWFLOW_RECORD_VOICEMAIL_SAVE_FIELDS
Line 279 LAWFLOW_RECORD_VOICEMAIL_SAVE_FIELDS
Line 280 LAWFLOW_RECORD_VOICEMAIL_SAVE_FIELDS

Call block

Webhook Trigger

webhook_trigger

Runtime tested / requires configured endpoint

What this block does

Calls a configured webhook/API endpoint and routes based on the result.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
Webhook URL	`webhook_url`	No	text
Webhook Method	`webhook_method`	No	POST
Database Payload JSON	`database_payload`	No	json
Save Target	`save_target`	No	master_call_record
Save Mapping JSON	`save_mapping`	No	json
Next Step	`next_step`	No	follow_connected_edge

Runtime behaviour

Calls a configured webhook/API endpoint and routes based on the result.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Runtime source reference needs manual confirmation.

Call block

Yes / No Check

yes_no_check

Runtime ready with required config

What this block does

Routes the call based on a yes or no answer.

When to use it

Use this block when this step is required in the caller workflow, then connect each output route to the correct next block.

Expected inputs

Input	Config/source field	Required	Example / note
input_source	`input_source`	Check settings
route_labels	`route_labels`	Check settings

Runtime behaviour

Routes the call based on a yes or no answer.

Outputs

Output field	Saved location	Example / note
Configured save target	Depends on block settings	Usually master_call_record or a workflow-specific table.

Routes

Route label	Meaning	When used
Next	Continue to the next connected block.	Default successful path.

Failure handling

If required configuration or runtime data is missing, the block should use its Error/Failure/Missing Info route where configured, or stop safely with an audit/log entry.

Runtime reference

Line 401 LAWFLOW_YES_NO_CHECK_CAPTURE_FIELDS_V1
Line 402 LAWFLOW_YES_NO_CHECK_CAPTURE_FIELDS_V1
Line 408 LAWFLOW_YES_NO_CHECK_CAPTURE_FIELDS_V1