Weddingkart Changelog

For every guest whose number you don't have yet - the cousin nobody saved, the extended family only your parents know - create an invite link instead of chasing a phone number.

• Generates a matching QR code (PNG for digital, SVG for print on the patrika) alongside the link
• Guests with WhatsApp tap through and add themselves in one chat; a short web form covers guests without WhatsApp
• Create more than one named link - each can auto-add joiners into different WhatsApp groups
• Turn on approval per link so new joins wait for your yes before they count
• Disable or revoke a link any time - a printed QR code just stops working until you re-enable it

Misconfigured S3 uploads used to surface as "the call rang, the guest answered, then heard nothing". We now HEAD the asset URL right after upload and refuse the campaign if anything looks off.

• HTTP 200 + Content-Type starts with audio/ + Content-Length > 0 = pass
• 404 / wrong MIME / zero-byte = upload rejected with a planner-friendly error
• Stops broken campaigns before any guest is dialled

Webhooks are how telephony and messaging providers tell us "this guest answered", "the call ended", "RSVP collected". If those endpoints are unauthenticated, anyone who learns the URL can forge any of those events.

• Twilio voice webhooks: HMAC-SHA1 verified via X-Twilio-Signature
• ElevenLabs voice agent webhooks: HMAC-SHA256 verified via ElevenLabs-Signature timestamp+v0 scheme
• WhatsApp inbound: signature + timestamp validated against per-tenant secret
• Unsigned or replay-after-window requests are rejected at the edge before any DB write

Telephony providers bill for the dial attempt, not the conversation. We now intercept that and treat it the way a planner expects.

• Refund triggers on Twilio terminal-no-airtime statuses (busy, failed, no-answer, canceled)
• Idempotent — re-firing the same status webhook will never double-credit
• Visible on the campaign report as "refunded" against the original charge

Set up a voice campaign once, define what you want to know, and Neeti handles the rest.

• Natural Hindi-English conversation, no scripts
• Editable goal schema per campaign (RSVP / count / dietary / hotel / anything)
• Captured answers land in the guest record AND a per-call "What we learned" panel
• Picks up the right family context (groom / bride / venue) from your wedding details
• Sub-second response latency on the latest voice model

Photo collection mode lights up a Drive-backed shared folder per wedding so guests can push their photos in without anyone managing uploads or albums.

• One-tap connect to Google Drive
• Empty-state walkthrough so the first-time experience teaches the feature
• Works alongside the existing announcement / RSVP flows

• Bot Hub home screen with bot health, recent answers, and pending nudges
• Knowledge editor: paste FAQs, venue details, dress code; the bot uses them as ground truth
• Settings to control tone, escalation thresholds, and which numbers it answers from
• Suppression chip on the chat — silence the bot for a specific conversation in one tap
• Pending nudges queue surfaces conversations where the bot is uncertain so a human can step in

• Shared PDFs render locally — the file no longer transits a third-party viewer
• Auth token migrated transparently into iOS Keychain / Android Keystore (hardware-backed where available)
• No action required from existing users; the migration runs once on next launch

• Pin and mute conversations from the inbox; new Unread filter chip
• Long-press a message for Copy / Forward; bulk-select for multi-message actions
• Tap any chat image for a fullscreen pinch-zoom viewer
• Scroll-to-latest floating button
• Quick-jump shortcuts to a guest’s RSVP, Travel, or ID Card from inside the chat
• Bubble polish to match WhatsApp spacing, tail, and tick states

The new series covers AI guest management, planning tools, communication, voice AI, and diaspora weddings (UAE, UK, US, Canada).

One new article every 2 days from 19 April to 8 June 2026 - fully automated, no manual work needed.

• 27 articles
• Quick-answer summary and FAQ on every page
• Branded hero images on every page
• Each page goes live automatically on its scheduled date

Couples and planners who already run a WhatsApp Business Account can now plug it straight into Weddingkart.

• Facebook embedded signup flow (OAuth)
• Auto-detects phone numbers + templates on the connected account
• Works across the mobile app and the web guest experience

These headers ship on every response from next.config.ts, so they apply uniformly to blog posts, tools, real-wedding pages, and the changelog itself.

• HSTS with includeSubDomains and preload
• X-Content-Type-Options: nosniff (blocks MIME sniffing attacks)
• Referrer-Policy: strict-origin-when-cross-origin
• Permissions-Policy locked down to the minimum surface

Finding the right message frame used to require scrolling a flat list.

• Tabbed categories (My, Recommended, Community)
• Edit-in-place before sending
• Guest search + debounced filtering

• WhatsApp templates hub + cross-links from blog
• Save the Date in 12 languages (Arabic and Malayalam added)
• Quick-answer summaries added to related blog posts

For a 300-guest Indian wedding, voice AI closes the RSVP loop in days instead of weeks.

• Multi-language: Hindi, English, with regional languages rolling out
• Captures headcount, dietary preferences, travel detail
• Updates the guest dashboard automatically

• Full CRUD on announcement schedules (create, pause, resume, activate, recover deleted)
• Critical alerts + today’s tasks + progress overview on wedding detail
• Deleted announcements recovery
• Phone numbers now parsed in E.164 format

• Razorpay integration + order creation API
• Top-up flow for paid weddings
• GST on payments
• Transaction history
• Sentry for payment failure capture

• CSV + Excel guest upload with cleanup
• WhatsApp broadcast templates by category
• Announcement packs with recommendations
• Guest selection, RSVP tracking and home progress