Ask
Brenneck Pay: documents logo

Brenneck Pay usage and what merchant risk needs next

Email thread

Brenneck Pay: documents logo Brenneck Pay: documents · cs

Katrin Vogelsang reported 33 active users of 40 and seven of eight connectors configured. Aylin Kaya wants a case tool and a chargeback feed, which Katrin thinks exceed Growth. She wants Matteo Ricci involved early and EU residency kept.

What was said

What this says

Current to 11 Oct 26

Katrin Vogelsang reported 33 active users of 40 and seven of eight connectors configured. Aylin Kaya wants a case tool and a chargeback feed, which Katrin thinks exceed Growth. She wants Matteo Ricci involved early and EU residency kept.

Ask: Katrin asked for the source of the Growth limit and the options for a case tool and chargeback feed. She also asked for a written agenda, minutes with named actions, and an early discussion without waiting for the next review.

Customer view: The team is very pleased with the brain and wants momentum. EU data residency must hold for anything new.

Next: Elena confirmed neither item is in Growth as contracted and wants checks with product and engineering before answering. Matteo owns the commercial side.

AI · claude-sonnet-5-5 · 11 Oct 2026

The thread

Updated 9 Oct 26
Typecs
Messages3
First message2026-06-02
Last message2026-06-04

Messages

  1. Katrin Vogelsang
    Katrin Vogelsang 2 Jun 2026 10:50
    to Elena Novak
    Dear Elena, I wanted to write to you before our next review, because the picture here has changed since we went live and I would like it to be on record. To be precise, we now have thirty-three active users, against forty licensed, and seven of the eight connectors are configured. Account management uses the merchant view daily. Merchant risk has joined in the last weeks, and that is where the new demand comes from. Aylin, who is copied, has been working with the brain on merchant files and she has two requests: 1. A case tool, so that a risk review of a merchant is opened, worked and closed in the same place where the merchant is seen. 2. A chargeback feed, so that chargebacks sit next to the payment and account data we already have. As far as I can tell, both go beyond what Growth includes. What is the source of that limit, and what are our options? I would rather understand the position properly than assume. One more point: the data must stay in the EU region, as agreed at the start. Please keep that in mind for anything new. Let us agree the next step. Could you come back to me with what you need from us? Kind regards, Katrin
  2. Elena Novak
    Elena Novak 2 Jun 2026 12:21
    to Katrin Vogelsang, Aylin Kaya
    Dear Katrin, dear Aylin, Thank you for the clear summary, and good news on the adoption. I have copied Matteo, who owns the commercial side of your account. To confirm where we stand: 1. Your current Growth subscription covers forty users and eight connectors. You are inside both limits, so there is no issue there. 2. The case tool and the chargeback feed are not part of Growth as it is contracted today. I will not give you an answer on how they would be provided until I have checked it with our product and engineering colleagues. 3. The EU data residency stays as agreed. I will make sure that any proposal respects it. What I need from you, Aylin, is a short written description of how a merchant risk review runs today, which fields the chargeback data contains and which system it comes from. With that, Matteo and I can come back with something concrete rather than a general answer. Matteo, please let me know if you would prefer to take the options discussion yourself. Kind regards, Elena
  3. Katrin Vogelsang
    Katrin Vogelsang 4 Jun 2026 15:32
    to Elena Novak
    Dear Elena, Thank you, this is helpful and exactly the structure I hoped for. Aylin has written up the review process and the chargeback fields, and she will send them to you directly today. The source is our payment platform's dispute export, and she has noted that in the document. Two requests from my side: 1. Please send a written agenda before we meet, and the minutes afterwards, with a name and a date for each action. I need this for our own records and for the auditor. 2. Please do not let this wait for the next scheduled review. If Matteo can join, I would like to settle the direction early. On the whole, the team is very pleased with the brain, and I would like to keep that momentum going. Kind regards, Katrin

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain 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 Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain 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.

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

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Brain · read-only