Contact

Common questions

What problem does this product focus on?

Helping ski-related businesses (resorts, ski schools, rental shops, regional winter operators) win relevant pre-season traffic and bookings online: earlier in the trip-planning cycle, with messaging that competes for the right intent, and with a full funnel (not only one social channel) against bigger digital budgets.

How is this different from a generic chatbot?

The agent is scoped to that job: pre-season calendars, search and content angles vs. aggregators, and coordinated funnel assets (email, paid, organic, remarketing, booking CTAs). It is not open-ended trivia or generic copywriting.

Who is it for?

Owners and marketers at independent or regional ski businesses: areas, ski and ride schools, rental and retail shops, lodging or tourism boards tied to a winter economy. Agencies serving those clients can use it too.

Are API keys exposed in the browser?

No. Keys and secrets live only in server environment variables (for example Vercel project settings or a private .env.local). Never prefix them with NEXT_PUBLIC_, which would bundle them into client-side JavaScript. The chat and product MVPs call your own API routes; those routes talk to OpenAI on the server.

Do I enter API keys every time I use an agent?

No. Add OpenAI credentials once to your server environment (see .env.example). The public agents keep working on every visit without any key field in the UI. If the key is missing, you will see a notice on the agent page and offline-style fallbacks where applicable.

Will it run my ads or send email for me?

No. You get drafts, structures, and checklists to implement in your tools. You approve what goes live.

Can I cite statistics the agent mentions?

For regulated or brand-sensitive copy, verify any numbers (for example shares of digital trip planning) against sources your legal or brand team accepts before publishing.