Feature identified in the platform code in October 2026. Availability depends on the deployed version, permissions and environment connectors. Contact Zild if it is not visible yet.
What changed
Configure tools to load customer context, look up rides and request a new ride. The request contract also supports forwarding an e-ticket code and password when supplied by the workflow.
How to use it
In the tool wizard, associate the Original Software connector and configure required request fields. Separate fixed values from data-collection instructions. Confirm name, pickup and other information before allowing a real request. In the October 23 update, the integration contract gained optional ETicketCodigo and ETicketSenha fields, forwarded to the source system. Confirm their mapping in the workflow you use.
Limits and prerequisites
The passenger phone comes from the conversation, not an arbitrary model choice. Unconfigured fields are not sent. Company codes, employee IDs and vouchers must preserve the expected format; credentials must not be repeated to the customer. Forwarding e-ticket fields does not establish issuance, balance, validity or acceptance; check the Original Software response. Availability in a form or agent depends on configuration.
Validate in your operation
Run an authorized simulation, verify data before submission and inspect the resulting ride. Define human handover for ambiguous addresses or missing required information.
Retrospective edition 2026-W43. The week identifies this collection’s editorial organization; the text was prepared on the date shown above.
Bring this idea into your operations.
Map the process, connect systems and evaluate outcomes with Zild.
Talk to an expert