> 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/storylane-playbooks/awareness-stage/conferences-trade-shows.md).

# Conferences/Trade Shows

<div align="left"><figure><img src="/files/cgukzhE9v96Vpy5QhrRy" alt="" width="563"><figcaption></figcaption></figure></div>

### The Goal

Engage attendees with interactive demos, increase comprehension, and establish a strong brand presence.

<div align="left"><figure><img src="/files/AJr7OotTrqkmxU4GvMnV" alt="" width="375"><figcaption></figcaption></figure></div>

## Implementation Guide

### 1. **Conference Mode**

Make sure to leverage Storylane’s distinct conference mode feature set.

* **Autoplay**: As people pass by your booth, let the demo reel them in with autoplay. If they want to interact with the demo, they can simply click through it along with the autoplay.
* **Fullscreen Mode**: Ensure the demo visually dominates, enabling easy viewing even from a distance.
* **Offline Mode**: With unpredictable internet connections at conference venues, Storylane's offline mode ensures your demos run seamlessly, allowing continuous engagement without any hitches.

### 2. Demo Structure

* Utilize Storylane's image modals to welcome users, tooltips, and walkthroughs to showcase your product's key features.
* Make sure the demo has no more than 10 steps. If it's not possible, segment it into multiple [flows](https://docs.storylane.io/storylane-knowledge-base/demo-editor/guides-and-flows/flows-and-product-tour) and let viewers pick their own adventure.
* Tailor the demo to fit the theme of the conference, ensuring relevance and resonance with the attendees. This customization will also help in aligning your product's capabilities with the prevailing discussions and interests at the event.

### **3. Live Demonstrations**

* If possible, schedule live demo sessions utilizing Storylane's fullscreen presentation feature.
* Engage the audience with live Q\&A sessions post-demonstration.

### **4. Post-Conference Distribution**

* Share the demo with attendees post-conference, offering a personalized experience based on the information collected.
* Utilize Storylane’s analytics to track engagement and gather insights for future follow-ups.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.storylane.io/storylane-playbooks/awareness-stage/conferences-trade-shows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.