Repetition of shipment details
A request to repeat returns the conversation to the shipment information. Origin, destination, product, quantity and urgency remain available in the call context.
From shipment dispatch to a conversation with the recipient.
An American Red Cross proof of concept for automated calls about blood-product shipments. Amazon Connect starts the call, Polly reads the shipment details, and Lex V2 routes the recipient’s requests through four supported conversation paths.
A request to repeat returns the conversation to the shipment information. Origin, destination, product, quantity and urgency remain available in the call context.
Lex recognises a request for more information and routes it to the configured response. The prototype answers within the shipment details supplied to the notification scenario.
The change-order intent selects its own branch in the contact flow. Recognising this request does not itself modify the order; that action belongs to a separate operational process.
The supported ending path plays the closing message and terminates the call. Separate fallback and error routes handle responses or execution states outside the expected path.
Call orchestration, speech and intent routing connected in a focused AWS proof of concept.
Amazon Connect runs the contact flow. Lambda, Fastify, Node.js and the AWS SDK connect it with the notification service.
Polly speaks the notification. Lex V2 recognises the configured recipient requests and routes the conversation.
IAM defines the access granted to the AWS services involved in the prototype.
Define the trigger, the shipment data and the recipient’s likely requests. We can build a focused call scenario and agree how to review its outcomes before adding more responsibilities.
Plan a voice pilot