Llano Crossing Software / BG-Demo – Onboarding
Callcompleted
Llano Crossing Software · 8 Jul 2026 14:00
A week into implementation, Hamza Akhtar and Hector Villarreal worked through the product analytics schema. The first load is due overnight with only a recent window of product data, and Kayla Ramirez queried why.
What was said
What this says
As at Fri 9 Oct 2026A week into implementation, Hamza Akhtar and Hector Villarreal worked through the product analytics schema. The first load is due overnight with only a recent window of product data, and Kayla Ramirez queried why.
What happened: Hamza checked connector progress. Hector confirmed helpdesk and Salesforce access was given, and flagged a legacy field in the event logs that sometimes holds an email instead of a user ID. Hamza will add a transformation to normalise it.
Customer view: Kayla asked why only a week of product analytics would load first. She wanted to know how the nightly refresh works and when to start getting people on.
Commercial: Value depends on the data flowing cleanly. Hamza set a three-day error-free window before the historical backfill is expanded, and said users can onboard by next week.
Watch: The brain is a nightly snapshot, so tickets arriving before the 07:00 refresh will not show until the next day. Hamza also asked the customer to report any connector that stops pulling data.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Hamza Akhtar to finish the product analytics mapping that night and start the first load the next day.
- Hamza Akhtar to send a progress email the next day and reconvene on Thursday.
- Hamza Akhtar to send Kayla Ramirez a user guide and quick-start queries.
Risks
As at Fri 9 Oct 2026- The legacy event log field mixing emails and user IDs could cause data quality issues if the transformation is wrong.
- Starting with about a week of product analytics may disappoint Kayla Ramirez until the history is expanded.
Opportunities
As at Fri 9 Oct 2026- Users can start onboarding by next week once data is stable, which lets adoption start early.
Transcript
Hamza AkhtarHi Hector, Kayla, thanks for joining. So we're a week into implementation and I wanted to check in on the connectors. How's everything looking on your side?
Hector VillarrealPretty good. We got you the helpdesk and Salesforce access last week. The product analytics schema is a bit complex on our end, I sent over the documentation.- Hamza AkhtarI got it. Thanks. I've mapped most of it, but there are a couple of fields I want to clarify, the user ID field, for instance. Is that consistent across all tables?
- Hector VillarrealYeah, it's pretty consistent. It's our internal user ID. I can walk you through the exceptions if needed.
- Hamza AkhtarThat'd be helpful. Let me share my screen and you can show me what I should look for.
- Hector VillarrealSure. So here, the main users table is clean, but we have a legacy field in the event logs that sometimes uses an email instead of the ID. You'll want to handle both.
- Hamza AkhtarGot it. I'll add a transformation to normalise that. It's not uncommon.
Kayla RamirezSo when will the data actually show up in the brain?- Hamza AkhtarOnce I finish the mapping, probably by tomorrow, the first load will run overnight. So by Thursday morning you should see helpdesk and Salesforce data, and maybe a week of product analytics.
- Kayla RamirezA week? Why just a week?
- Hamza AkhtarWe load historical data in a backfill, but we start with a recent window to get you results quickly. Once the first load is stable, we'll pull more history.
- Hector VillarrealHow stable are we talking?
- Hamza AkhtarWe'll run for three days with no errors. If everything's clean, no duplicate records, data quality issues, then we'll expand the historical window.
- Kayla RamirezOkay. And the nightly refresh, how does that work once we're live?
- Hamza AkhtarWe'll sync your systems every night by 07:00 your time on business days. So helpdesk, Salesforce, and your product analytics all update in one shot.
- Hector VillarrealDo you need anything from us once it's live?
- Hamza AkhtarNope. It's automated. But if you notice a connector isn't pulling data, like tickets stop appearing, let us know. We monitor it, but you'll often see it first.
- Kayla RamirezGot it. And what about user access? Should we start getting people on?
- Hamza AkhtarYeah, once data is flowing and stable, so probably by next week, you can start onboarding your team. I'll send you a user guide and some quick-start queries to help them get oriented.
- Kayla RamirezAre there any gotchas I should know about?
- Hamza AkhtarA couple of things. First, the search interface works best with concrete questions, like 'show me customers with high ticket volume', rather than vague ones. Second, the data is a nightly snapshot, so if someone's working with tickets that came in at 06:00 in the morning, you won't see them until tomorrow.
- Hector VillarrealThat makes sense.
- Hamza AkhtarAlright. So my next move is to finish the product analytics mapping tonight, kick off the first load tomorrow, and we'll reconvene Thursday to see how it looks.
- Kayla RamirezSounds good.
- Hamza AkhtarThanks both. I'll send you a quick update email tomorrow with progress, and we'll chat Thursday. Cheers.