Skip to content

[$175] Scheduled call isn't displayed after booking via Calendly #106380

Open

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: v9.5.34-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #105868
Email or phone of affected tester (no customers): applausetester+luc1@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11 Home / Chrome
App Component: Other

Action Performed:

  1. Open https://staging.new.expensify.com/
  2. Sign in with expensifail account
  3. Open chat with Concierge
  4. Click Book a call
  5. Complete booking with Calendly
  6. Navigate back to chat with Concierge

Expected Result:

After booking a call, the scheduled meeting should be displayed in the chat.

Actual Result:

After completing the booking via Calendly, the user is redirected to the login page at https://use.expensify.com/travel. The scheduled meeting isn't displayed in app, and the Book a call option remains unchanged.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7309123_1794235287194.Recording_2026-11-09_153621.1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7309123

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @marcaaron

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 9, 2026
  2. applause-bot commented on Nov 9, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/ec97a29ded646ed269955de5213bbc63f71dd45c75d896e9dc1252aa5e5c11f5

  3. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Nov 9, 2026
  4. melvin-bot commented on Nov 9, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @huult (External)

  5. changed the title [-]Scheduled call isn't displayed after booking via Calendly[/-] [+][$175] Scheduled call isn't displayed after booking via Calendly[/+] on Nov 9, 2026
  6. melvin-bot commented on Nov 9, 2026

    @melvin-bot
  7. MelvinBot commented on Nov 9, 2026

    @MelvinBot
    Contributor

    🤖 Web test steps verification results: ⚠️ partial

    The supplied web account could open Concierge, but had no “Book a call” button, so the reported booking failure could not be reproduced. Preliminary analysis: the unchanged button is explained by App code; the missing meeting and travel redirect remain unverified.

    Concierge history without a Book a call CTA

    Step Status
    1–2: Open app and confirm signed-in sessionAuthenticated successfully using the supplied account, which differs from the original reporter’s account.
    ✅
    3: Open Concierge chatConcierge opened, but no booking button was available.
    Concierge history without a Book a call CTA
    ✅
    4–5: Inspect booking destination and redirectBlocked by the absent button; no appointment was created.
    Code findings: Concierge chooses an account-provided calendar link in HeaderView.tsx:259–317. BookCallButton.tsx:33–72 opens that link unchanged and always renders the same label. Therefore, an unchanged button does not establish that booking failed.
    Alternative considered: the guided onboarding scheduler is a different flow: it adds identity and report-association parameters in ScheduleCall.ts:75–83. Comparing its scheduled-call display with Concierge’s external-link button may conflate two behaviors.
    ⚠️
    6: Return and inspect scheduled meeting / buttonCompletion-dependent behavior remains unverified. Scheduled-call rendering depends on report data read by ReportNameValuePairs.ts:73–75; returning from Calendly alone does not demonstrate that this data was created.
    Blocker: production log tools were unavailable, so booking/webhook processing could not be checked.
    Recommended next step: capture the affected account’s actual Calendly URL, successful booking confirmation, booking timestamp, and report/event IDs. An internal engineer should then verify the external redirect configuration and booking-to-report association. There is insufficient evidence to recommend an App fix or attribute this to the date-localization PR.
    ⚠️

    view run

  8. kevinjosh10 commented on Nov 9, 2026

    @kevinjosh10

    Proposal

    What is the root cause of that problem?

    This is a missing parameter gap between the Concierge header button and Expensify's Calendly webhook ingestion service:

    1. Missing utm_content=${reportID} in BookCallButton.tsx:
      In Expensify's architecture, when a user books a call via Calendly, the Calendly webhook updates the client by writing to reportNameValuePairs.calendlyCalls. To know which report to associate the booking with, the backend webhook parses the query parameter utm_content.

      • In the guided onboarding flow (src/libs/actions/ScheduleCall.ts:75–83), NewDot correctly enriches the Calendly URL with report context:
        const calendarUrl = `${link}?name=${encodeURIComponent(currentUser.displayName)}&email=${encodeURIComponent(currentUser.login)}&utm_source=newDot&utm_medium=report&utm_content=${data.reportID}&timezone=${timezone}`;
      • In src/components/BookCallButton.tsx:47, clicking the Concierge header button simply calls openExternalLink(calendarLink).
      • Because BookCallButton opens the raw calendarLink without utm_content=${report.reportID}, the Calendly webhook receives the booking payload with no report identifier. The webhook is unable to map the call to the chat session, so reportNameValuePairs.calendlyCalls is never populated in Onyx.
    2. Redirect Destination:
      The redirect to /travel is configured directly on that Calendly event's confirmation redirect settings in Calendly's administrative dashboard.

    What changes do you think we should make in order to solve the problem?

    1. In src/components/BookCallButton.tsx:
      Accept reportID?: string, currentUserEmail?: string, and currentUserDisplayName?: string (or read from Onyx session/personal details):

      const getEnrichedCalendarLink = (link: string, reportID?: string, email?: string, name?: string) => {
          if (!link) {
              return '';
          }
          try {
              const url = new URL(link);
              if (reportID) {
                  url.searchParams.set('utm_source', 'newDot');
                  url.searchParams.set('utm_medium', 'report');
                  url.searchParams.set('utm_content', reportID);
              }
              if (email) {
                  url.searchParams.set('email', email);
              }
              if (name) {
                  url.searchParams.set('name', name);
              }
              return url.toString();
          } catch {
              return link;
          }
      };
    2. In src/pages/inbox/HeaderView.tsx:300–317:
      Pass report?.reportID and user details into <BookCallButton>:

      <BookCallButton
          calendarLink={bookCallCalendarLink ?? ''}
          avatarAccountID={bookCallAvatarAccountID}
          reportID={report?.reportID}
          currentUserEmail={currentUserEmail}
          currentUserDisplayName={currentUserDisplayName}
      />
    3. Backend / Calendly Config Alignment:

      • On the Calendly dashboard, verify the confirmation redirect for the event type is set to return the user to NewDot (https://new.expensify.com/r/[reportID]) rather than the static /travel landing page.

    What alternative solutions did you explore? (Optional)

    • Treating this as solely a backend defect: While the webhook writes the NVP, the webhook cannot associate a report without the client transmitting utm_content=${reportID} in the first place. Enriching the URL on the client in BookCallButton.tsx mirrors ScheduleCall.ts and resolves the root omission.

    Tests

    1. Open a chat with Concierge on Web/Desktop/Mobile where "Book a call" is available.
    2. Tap "Book a call".
    3. Inspect the opened Calendly URL and verify that it contains:
      utm_source=newDot&utm_medium=report&utm_content=[reportID]&email=[userEmail]&name=[userName]
    4. Complete the booking.
    5. Verify the backend webhook receives utm_content and populates reportNameValuePairs.calendlyCalls, displaying the scheduled call card in the report header.


    Contributor details

    Your Expensify account email: lkevinjosh10@gmail.com
    Upwork Profile Link: https://www.upwork.com/freelancers/~0131dae36abcf59374

  9. TassioSales commented on Nov 9, 2026

    @TassioSales

    Contributor details
    Your Expensify account email: tassiolucian.ljs@gmail.com
    Upwork Profile Link: https://www.upwork.com/freelancers/~0179cdc82689f205c7

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    After scheduling an advisory call through the embedded Calendly widget, the scheduled call confirmation card is not displayed in the app.

    What is the root cause of that problem?

    The embedded Calendly iframe/webview communicates successful booking via window.postMessage (calendly.event_scheduled). The message listener in the Calendly wrapper component either misses the event due to an origin mismatch or fails to invoke the Onyx action that updates account.scheduledCall / policy.scheduledCall, resulting in no reactive re-render of the scheduled call banner.

    What changes do you think we should make in order to solve the problem?

    1. In src/components/CalendlyWidget/index.tsx, ensure the message event handler verifies data.event === 'calendly.event_scheduled' and reliably extracts booking details.
    2. Call User.setScheduledCallDetails() or appropriate Onyx action upon receiving the event to persist the call timestamp in Onyx.
    3. Ensure the home page and workspace tiles reactively observe the scheduled call state and render the confirmation card.

    What alternative solutions did you explore? (Optional)

    • Polling the backend for scheduled call status: Rejected because WebSocket/postMessage event listening is instantaneous and avoids unnecessary polling network overhead.

    What automated tests can you add to prevent this from re-occurring?

    In tests/unit/CalendlyWidgetTest.ts:

    • Add a test verifying that dispatching a simulated calendly.event_scheduled message updates Onyx with the correct scheduled call payload.
  10. melvin-bot commented on Nov 9, 2026

    @melvin-bot

    ✅ Contributor details stored successfully. Thank you for contributing to Expensify!

  11. huult commented on Nov 10, 2026

    @huult
    Contributor

    @MelvinBot Please create the proposal.

  12. MelvinBot commented on Nov 10, 2026

    @MelvinBot
    Contributor

    Proposal

    ⚠️ Draft — not ready for implementation. The App behavior is established, but the missing meeting and travel redirect still need confirmation.

    What is the root cause of that problem?

    The reported Concierge button opens an account-provided calendar link and does not observe booking status. Its unchanged label therefore does not prove that booking failed.

    The separate onboarding scheduler supplies report-association parameters, but there is no verified evidence that omitting those parameters caused this booking to disappear. The travel redirect’s source is also unconfirmed.

    Current code additionally replaces Concierge’s booking button with “Talk to a human,” so the affected version and intended behavior need clarification.

    Code evidence

    What changes do you think we should make in order to solve the problem?

    Before selecting a code fix:

    1. Confirm whether this behavior remains reproducible with the current Concierge action.
    2. Capture the affected calendar URL, successful booking confirmation, timestamp, Calendly event ID, and report ID.
    3. Have an internal engineer verify the completion redirect and whether the booking was associated with the intended report.
    4. Confirm whether Concierge bookings should produce a chat message or a scheduled-call dropdown.

    Adding URL parameters alone is not a complete fix: it would neither change the button’s label nor establish the expected meeting display. If the failure lies in backend processing or external Calendly configuration, escalate it to an internal engineer rather than implementing an App-only workaround.

    What alternative solutions did you explore? (Optional)

    • Match onboarding URL parameters: potentially relevant, but backend association requirements remain unverified.
    • Handle an embedded Calendly completion message: does not match the inspected external-link implementation; the proposed widget and action were not found.

    Validation blocker: the previous web test account lacked the booking button, and production logs were unavailable. No end-to-end booking failure has been independently confirmed.


    view run

  13. huult commented on Nov 10, 2026

    @huult
    Contributor

    The "Book a call" button only opens the backend-provided Calendly link (openExternalLink(calendarLink)), so the /travel redirect and the missing scheduled call (reportNameValuePairs.calendlyCalls) are set by Calendly config and backend webhook data, not the App. This looks like a backend issue, and PR #105868 (date formatting only) isn't the cause.

    So I think we should ask an internal engineer to help investigate this issue. Let me know if there's anything I can help with.

    🎀 👀 🎀 c+ reviewed.

  14. melvin-bot commented on Nov 10, 2026

    @melvin-bot

    Triggered auto assignment to @marcaaron, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  15. kevinjosh10 commented on Nov 10, 2026

    @kevinjosh10

    Hi @huult, thanks for looking into this!

    Just to add some quick context alongside @MelvinBot's analysis:

    MelvinBot is spot on that the Concierge CTA is strictly an external URL launcher (BookCallButton.tsx:19–58), confirming that proposals relying on an embedded Calendly widget or postMessage listener are non-applicable to this codebase.

    As detailed in my proposal above, there are two clear paths depending on the intended product design:

    1. If the booking is intended to reflect in the App: In NewDot, scheduled calls are not rendered as chat messages; they appear in the header dropdown (OnboardingHelpDropdownButton.tsx) when populated via reportNameValuePairs.calendlyCalls. For backend webhooks to map the completed Calendly booking back to the report, BookCallButton simply needs to pass the report context (utm_content=${reportID} & identity parameters), exactly like the guided onboarding flow does in ScheduleCall.ts:75–83.
    2. If the button is purely an external scheduling link: Then the unchanged button is expected behavior (NAB), as an external Calendly tab cannot notify the App without that report association.

    If the team wants to proceed with enriching BookCallButton to support report linkage, I already have the branch tested and ready. Happy to proceed whichever way you prefer!

  16. huult commented on Nov 13, 2026

    @huult
    Contributor

    @stitesExpensify I saw you're working on the travel project. What do you think about this?

  17. stitesExpensify commented on Nov 14, 2026

    @stitesExpensify
    Contributor

    Thanks @huult, I agree with you on both points. This isn't an App bug, and the use.expensify.com/travel redirect is coming from the Calendly event settings, not our code. I dug in a bit more on the missing booking, and here's what's going on.

    The "Book a call" button in Concierge just opened the guide's Calendly link as a plain external link. It was never set up to report the booking back to the app. The scheduled call you see in the app only comes from the in-app scheduler in #admins. That flow tags the Calendly link with the admins room, and the backend only saves bookings that carry that tag. Concierge bookings are skipped on purpose, so nothing was ever going to show up there. That matches the original PR (App #97486), which describes the button as an external Calendly link and leaves the #admins booking flow alone.

    Also, this is basically moot now. App #105055 swapped "Book a call" in Concierge for "Talk to a human" for everyone, so the button from the test steps isn't there anymore.

    @zanyrenney @JmillsExpensify since you were both on the original Book a call work (Expensify #665368), can you confirm we never meant for a booking made from Concierge to show up in the app? If that's right, I think we can close this out.

  18. expensify-chore-bot commented on Nov 17, 2026

    @expensify-chore-bot

    @marcaaron 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  19. huult commented on Nov 18, 2026

    @huult
    Contributor

    @zanyrenney @JmillsExpensify since you were both on the original Book a call work (Expensify #665368), can you confirm we never meant for a booking made from Concierge to show up in the app? If that's right, I think we can close this out.

    cc @zanyrenney @JmillsExpensify

  20. JmillsExpensify commented on Nov 18, 2026

    @JmillsExpensify
    Contributor

    I defer to Zany on that one. I'm not very familiar with this project.

  21. expensify-chore-bot commented on Nov 19, 2026

    @expensify-chore-bot

    @marcaaron Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorOverdue

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions