> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/repx-updates/july-28-2026.md).
# July 28, 2026
Hey Storylaners! Quick replies that make it easier for your visitors to respond and Zapier, webhooks to push conversation data anywhere.
### ↪ Quick replies
RepX now shows **clickable answer suggestions** whenever it asks questions to visitors**.** With quick replies, your users can easily engage further without having to type out their responses. \
\
Quick replies are AI-generated automatically, based on the content you've trained RepX on and the current question being shown.
### ⚡ Zapier integration
RepX conversation data can now be pushed anywhere Zapier reaches.
When a conversation completes, we fire an event named 'RepX conversation completed' that reaches Zapier with the full picture:
* the **lead's email, name and phone number** if they've submitted them in the conversation
* the **company information** detected based on the visitor's IP
* conversation **intent**
* conversation **topics**
* conversation **summary**
* full **transcript**
* extracted **conversation variables**
* the **duration** of the conversation
* the **CTA that was clicked**
You can view the full payload and read about how you can setup a Zapier integration [here](https://docs.storylane.io/repx-chat/integrations/zapier).\
\
Some things our customers are already accomplishing through Zapier:
* Mapping custom conversation attributes - pain points, migration size, whatever you're collecting - into specific CRM properties, so the account executive walks into the call already knowing enough information
* Emailing the visitor their own transcript as soon as the conversation ends
***
### 🔔 Webhooks
**Webhooks** can now be setup to send conversation data to any third-party system you prefer. You can use webhooks to push data into any application that Storylane does not natively integrate with. \
\
This webhook is triggered every time a conversation gets over, and the full payload we send includes the **transcript, conversation summary, list of topics, the duration, etc.** \
\
You can learn more about webhooks [here](https://docs.storylane.io/repx-chat/integrations/webhooks).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.storylane.io/repx-updates/july-28-2026.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.