How long does SDK integration take?
Standard SDK integration takes 1-2 months. White-label apps take 2-3 months. Custom builds vary based on scope.
What languages are supported?
Currently available in 30+ languages including English, Spanish, French, German, Korean, Japanese, and more. New languages can be added easily.
Can the AI be trained on our content?
Yes. We customize the AI model by ingesting your content, products, data, tone of voice, and brand preferences.
What data do partners receive?
Full access to our insights dashboard including: customer queries, top attractions, user segmentation, heatmaps, and behavioral data.
Does it work offline?
Yes. Walking tours can be downloaded for offline use. Real-time AI features require connectivity.
What about API access?
Yes, we offer API access for partners who want to build custom integrations beyond our SDKs.
How does the AI handle factual accuracy?
iWander's AI is purpose-built for travel, trained on verified destination data and partner-curated knowledge bases. Content goes through review workflows before going live, and the AI is designed to say "I don't know" rather than fabricate information. Partners can flag and correct responses at any time via the dashboard.
What happens when a traveller asks something outside the destination scope?
The AI stays on-brand and on-topic. If a question falls outside the destination or partner scope, it gracefully redirects the conversation back to relevant travel content rather than going off-topic. You control the boundaries.
Can the AI recommend and upsell partner experiences?
Yes. The platform delivers contextual, location-aware recommendations — nearby restaurants, skip-the-line tickets, partner activities — at the moment of maximum intent. Our partners see a 20% click-through rate on contextual upsells, driving real ancillary revenue.
How do you handle data privacy and GDPR?
iWander is fully GDPR compliant. We don't store personal data without consent, and all analytics are anonymised by default. Partners get rich behavioural insights without compromising traveller privacy. We can provide a full Data Processing Agreement on request.
Does the AI personalise for different types of travellers?
Yes. The AI adapts to language, interests, and travel context. A family with children and a solo architecture enthusiast standing on the same corner will get different recommendations and stories. The more a traveller interacts, the more personalised the experience becomes.
What's the difference between SDK, white-label app, and API?
SDK integration lets you drop modular components (Chat, Tours, Maps) into your existing app. White-label gives you a fully branded standalone app powered by iWander's AI under the hood. API access provides raw endpoints for fully custom builds. Most partners start with the SDK and expand from there.
Can we control the AI's tone of voice and brand personality?
Absolutely. We tune the AI to your brand guidelines — tone, vocabulary, personality, and even which topics to emphasise or avoid. The AI can sound like your brand, not ours.
How does the GPS-triggered audio work technically?
Audio tours use geofence-based triggering — when a traveller enters a configurable radius around a point of interest, the relevant audio plays automatically. Tours can be downloaded for fully offline use, so they work even without signal in tunnels, rural areas, or underground.
What ROI can we expect?
Our partners typically see 27% chat adoption rates, 28% uptake on free audio tours, 20% click-through on contextual upsells, and +13 minutes added to average session duration. All of this is measurable in real-time via the iWander data dashboard.
Do you work with attractions and DMOs, not just tour operators?
Yes. iWander's platform is designed for any business with an in-destination audience — tour operators, hop-on hop-off companies, attractions, hotels, DMOs, and cruise lines. If your customers are experiencing a place, we can help you engage them.
