> For the complete documentation index, see [llms.txt](https://tips.housewhisper.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tips.housewhisper.ai/prepping-and-managing-listings/add-leads-from-open-houses-seamlessly.md).

# Add Leads from Open Houses Seamlessly

Maximize ROI from your open houses with HouseWhisper's easy, flexible lead capture.

Got an open house coming up? Don’t waste a second transcribing contact information for your open house visitors into your CRM. Your HouseWhisper assistant processes lead information from photos in an instant, so you can bring your database up-to-date in no time. 

Here’s how it works:

### Create Open House Leads in Your CRM

1. Snap a photo of your open house sign-in sheet, business cards you received, or even handwritten notes you jotted down at the event.
2. Send the photo to your assistant and ask it to add the leads to your database.
3. Your assistant will reply and confirm the leads and information it has recognized, so that you have a chance to review before they are added. 

That’s it! No more manual entry for you, and no more fumbling with clunky iPad sign-in processes for your guests. HouseWhisper creates a seamless connection between your CRM and the people you meet during your day.

<br>


---

# 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://tips.housewhisper.ai/prepping-and-managing-listings/add-leads-from-open-houses-seamlessly.md?ask=<question>&goal=<user_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.