B-Viz
Hamza Akhtar

Larkspire Software / BG-Demo – Onboarding

Callcompleted

Larkspire Software logo Larkspire Software · 28 Jan 2026 09:00

The membership connector's record count went flat after the source system renamed two fields. Hamza remapped both, the sync resumed, and Kiran wants advance notice of future changes.

What was said

What this says

As at Fri 9 Oct 2026

The membership connector's record count went flat after the source system renamed two fields. Hamza remapped both, the sync resumed, and Kiran wants advance notice of future changes.

What happened: Kiran raised a ticket because the membership record count had not moved since the weekend. Hamza found a mapping problem, not an outage: the status field and the renewal date field had both been renamed at source.

Customer view: Kiran preferred a slow, correct fix to a guess, and will ask the membership team to warn BG-Demo before renaming anything. He is engaged and caught the fault himself from the export.

Commercial: Hamza said the ticket was non-urgent and, on Starter, was handled within its business-hours response. Nothing on price or renewal came up.

Watch: This is the second status field change, so more source-side changes are likely. The ticket should close only once the next refresh shows the count moving.

AI · claude-sonnet-5-5 · as at Fri 9 Oct 2026

Themes

As at Fri 9 Oct 2026
Theme
Membership connector mapping fault
Importance
neutral
Sentiment
neutral
Voice
user

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Hamza to close the ticket once tomorrow's refresh completes and the count moves.
  • Kiran to ask the membership team to tell BG-Demo before renaming any field.
  • Hamza and Kiran to keep a note of what changed and when.

Risks

As at Fri 9 Oct 2026
  • Further field renames at source could stall the connector again without warning.
  • Stale membership and renewal data would undermine trust in B-Viz.

Opportunities

As at Fri 9 Oct 2026
  • A change-notice process with the membership team would make the connector more dependable.
  • Quick diagnosis and a careful fix show support quality to the customer.

Transcript

  1. Kiran Bassi
    Kiran Bassi
    Morning Hamza. Thanks for making time at short notice.
  2. Hamza Akhtar
    Hamza Akhtar
    Morning. Of course. You said there's a ticket?
  3. Kiran Bassi
    Kiran Bassi
    One ticket, but it's a real one. The membership connector stopped picking up changes on Monday. The record count is flat.
  4. Hamza Akhtar
    Hamza Akhtar
    Flat as in not moving at all?
  5. Kiran Bassi
    Kiran Bassi
    Flat. Same number since the weekend. I checked twice.
  6. Hamza Akhtar
    Hamza Akhtar
    That's a good catch. A connector that stops loading usually means something changed on the source side. Did anyone touch the membership system?
  7. Kiran Bassi
    Kiran Bassi
    Yes. They changed the status field again. They told the membership team, but nobody told us. I found out from the export.
  8. Hamza Akhtar
    Hamza Akhtar
    Right. Let me look at the connector log. Give me a minute.
  9. Kiran Bassi
    Kiran Bassi
    Take your time. I'll make a coffee.
  10. Hamza Akhtar
    Hamza Akhtar
    Okay, found it. The status field has a different name now, and the connector is still looking for the old one, so it returns no new records. It's not an outage, it's a mapping problem.
  11. Kiran Bassi
    Kiran Bassi
    Good news, sort of. How long to fix?
  12. Hamza Akhtar
    Hamza Akhtar
    The fix is simple, a remap. But I want to check your list against the new export, so we don't miss a second field.
  13. Kiran Bassi
    Kiran Bassi
    Agreed. Don't guess. I'd rather it's slow and right.
  14. Hamza Akhtar
    Hamza Akhtar
    Let's look at the export. Share your screen?
  15. Kiran Bassi
    Kiran Bassi
    Sharing now.
  16. Hamza Akhtar
    Hamza Akhtar
    Found another one. The renewal date field has moved too. Two fields changed, not one.
  17. Kiran Bassi
    Kiran Bassi
    Brilliant. Of course.
  18. Hamza Akhtar
    Hamza Akhtar
    Not your fault. Let's remap both, then re-run the sync.
  19. Kiran Bassi
    Kiran Bassi
    Okay. Can we keep the old mapping for a day, in case the membership team changes something else?
  20. Hamza Akhtar
    Hamza Akhtar
    Yes. Keep a note of what changed and when. That's the useful bit for next time.
  21. Kiran Bassi
    Kiran Bassi
    Agreed. I'll ask the membership team to tell us before they rename anything, even if they think it's trivial.
  22. Hamza Akhtar
    Hamza Akhtar
    That's the right ask. Written action, if you like: membership changes come to us before they go live.
  23. Kiran Bassi
    Kiran Bassi
    Yes, put it in the notes.
  24. Hamza Akhtar
    Hamza Akhtar
    Re-running the sync now. Give it a few minutes.
  25. Hamza Akhtar
    Hamza Akhtar
    Records are coming through. The count is moving, and the renewal dates look right on the sample.
  26. Kiran Bassi
    Kiran Bassi
    Let me check. Yes, the status shows as active on the three I know. Good.
  27. Kiran Bassi
    Kiran Bassi
    So can we close the ticket? I'd like to tell the team.
  28. Hamza Akhtar
    Hamza Akhtar
    Close it once the next refresh completes. Tomorrow's refresh, before seven, should show the full picture. If it does, close it.
  29. Kiran Bassi
    Kiran Bassi
    Okay. I'll note it: close once tomorrow's refresh completes and the count moves.
  30. Hamza Akhtar
    Hamza Akhtar
    On response, this was a non-urgent ticket, which on Starter is measured in business hours. We were inside that, so no concern there.
  31. Kiran Bassi
    Kiran Bassi
    Good. I'd rather know than guess.
  32. Hamza Akhtar
    Hamza Akhtar
    Anything else before I go?
  33. Kiran Bassi
    Kiran Bassi
    No, I think that's it. Thanks Hamza.
  34. Hamza Akhtar
    Hamza Akhtar
    Thank you. Speak soon.
  35. Kiran Bassi
    Kiran Bassi
    Bye.

BG-Demo is a fictional company; every organisation and person here is invented. B-Viz is the tool. Data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Viz is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask B (the speech bubble) in the header, or open the Ask B page. Type a question, or pick one of the suggestions.

What the data covers

DataRecords
Organisations300
People at customers1,880
BG-Demo staff records (in post and leavers)65
Calls2,593
Email threads3,882
Support tickets1,502
Documents1,582
Deals403
Invoices365
Events49
News items147

Data as of Fri 9 Oct 2026. Text marked AI was written by the AI from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BG-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Viz is the tool that reads its data.

Who to contact

Email info@b-viz.com or talk to your B-Viz account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Viz · read-only