This release is built around two things. A critical bug fix that affected 25 invited guides who could not sign in to their accounts. And a full rework of the Guide Dashboard that puts every editable field for a guide profile in the guide's own hands, on mobile.
Critical Fix: Invited Guides Can Sign In Again
The guide invite flow had a quiet but critical bug. When an operator invited a guide from Settings, the platform created the guide record but did not create the associated authentication account. The guide received the invite email, clicked the magic link, and then hit a no-account-found error with no obvious recovery path.
The bug affected 25 guides across the platform. Some had been stuck for weeks.
The fix:
- The guide invite handler now creates an authentication user, generates a magic link, and links the auth user to the guide profile atomically in a single transaction.
- A one-time backfill script ran against every guide created before the fix who had no associated auth user. All 25 affected guides received a fresh magic-link email automatically.
- No action from the operator was required. The guides who were stuck received the new email at the address the operator originally invited.
If a guide is still seeing the no-account-found error after the fix, the operator can resend the invite from the Settings, Guides panel and the guide will receive a new working magic link.
Guide Dashboard Rework
The previous Guide Dashboard was a thin read-only view. A guide could see their own code, photo, and tip totals. To change anything, they had to ask the operator to update the guide record in admin.
The new Guide Dashboard makes the guide self-sufficient. Every field on a guide profile is editable from the guide's own login:
- Editable code. A guide can change their own access code. The new code is checked against the org's other codes for uniqueness, and the change propagates immediately to every guidebook the guide is assigned to.
- Photo and bio grid. Photo on the left, bio on the right, side by side on desktop and stacked on mobile. Both update the Meet Your Guide page on every guidebook.
- Phone and WhatsApp. Two separate fields. Phone renders as a "call" button on the guest-facing Meet Your Guide page. WhatsApp renders as a WhatsApp chat button.
- Payment platform manager. Add, remove, or reorder payment platforms. Venmo, Cash App, Zelle, PayPal, Apple Cash, Google Pay, and others. Each platform stores the guide's personal link or username and renders in its brand color on the gratuity page.
- Social link manager. Instagram, Facebook, TikTok, YouTube, X, LinkedIn, and other platforms. Each link renders as a brand-color button on the guide's profile.
- Mobile-responsive throughout. Guides can update their profile from their phone between tours.
The change is operator-aligned: operators do not want to be the bottleneck for guides who need to update their own payment link. The new dashboard removes that work from the operator's plate.
Tourist Guide-Code Attribution
The guest-facing side of the product got smarter about attributing engagement to the right guide. The improvements:
- Prefill from URL or session. If a guest opens a guidebook with a
?guide=CODEparameter, the code is treated as authoritative and the experience personalizes to that guide immediately. If no parameter is present, the previously stored code from the same session is used. - Stats attribution. Every tip click, review click, share event, and survey response is now tagged with the guide code, so the operator's analytics drill down by guide correctly.
- Org-level review fallback. If a guidebook has no review platforms configured but the operator's organization does, the org-level review links are used as a fallback so the leave-a-review page is never empty.
- WhatsApp button on the Meet Your Guide page when a guide has a WhatsApp number configured.
Smaller Wins in This Release
Other improvements that shipped alongside the guide work:
- About and FAQ pages rewritten on the marketing site for accuracy with current pricing.
- Joe Martin author byline and Article schema added to every marketing article for better attribution in search engines and answer engines.
- Referral box removed from the Billing and Plan page. The referral controls live in Settings, Referrals, and the duplicate was confusing operators.
- Email template em-dashes removed. Every email template was scrubbed of em-dash characters to match the broader copy style.
- Welcome email skipped for users invited as guides. Guides do not need the operator onboarding email, which was being sent in error and creating noise for invited team members.
Frequently Asked Questions
I invited guides before April 29 and they could not sign in. What happened?
A bug in the guide invite flow meant that invited guides were not getting an auth user record created when the operator sent the invite. The guide received an invite email, clicked the magic link, and then hit a no-account-found error. The fix went out on April 29. All 25 affected guides across the platform were automatically re-emailed with a working sign-in link. No action from the operator is required. If a guide is still seeing the error, they should ask the operator to resend the invite from Settings, Guides.
What can guides edit in their own dashboard now?
Guides can edit their own access code, photo, bio, phone number, WhatsApp number, payment platform links across Venmo, Cash App, Zelle, PayPal, and others, and their social media links. The dashboard is mobile-responsive so guides can update their profile from their phone between tours. Changes propagate immediately to the tourist-facing Meet Your Guide page on every guidebook the guide is assigned to.
Can guides accept tips through WhatsApp?
Guides can add their WhatsApp number to their profile, which renders a WhatsApp button on the tourist Meet Your Guide page. This is most useful for international tours where guests are more likely to use WhatsApp than text messaging. WhatsApp itself does not process tips, but a guide can use the channel to coordinate a tip handoff or share a payment link in conversation.
How does Digital Guidebooks attribute tips to a specific guide?
Each guide has a unique access code. Tourists enter the code on the access page or follow a guide-specific shareable URL with the code embedded as a parameter. Once a code is associated with a tourist session, every tip click, review click, share event, and survey response is attributed to that guide for the rest of the session. The attribution survives across page reloads and tab closes within a 24-hour window.
What changed about how guide selection persists for tourists?
If a tourist picks a guide from a multi-guide picker on a guidebook, the selection now persists across browser tab closures within the 24-hour access token window. Previously the selection was stored in session storage, which dropped when the tab closed. A guide-code passed in the URL is treated as authoritative and overrides any prior selection.
