Anchor partner

For the partner with a portfolio of garment makers (knitting mill, fabric distributor, spinner) and a benefits program: offer Tenka to customers as a benefit and, in return, read the portfolio — only what each customer consented to. You see who was invited, who created the account, who is using it and who stopped; and the consumption of YOUR input, aggregated by month and article.

Paste the portfolio, one line per customer: tax id; name; e-mail; program code. Each line becomes an invitation with a unique link, sent by e-mail. A tax id already in the portfolio is skipped; a line without a valid e-mail or tax id shows in the invalid list — nothing is swallowed. The customer creates the account through the link, already tied to the program, in the industry chosen in the invite.

Nothing (default): the account exists in your portfolio and that is all. Usage: you see last posting, last access and sales in the last 30 days — the health gauge. Aggregates: plus the consumption of your input, summed with other accounts by month and article. Orders: ready for the order-back, when it exists. The choice is the customer's, in Settings ▸ Sharing with the partner; they can revoke anytime, and revoking deletes what was published.

A group (month × article) only shows when it comes from K or more distinct accounts (REDE.K_ANONIMATO parameter, default 5). With few consenting accounts you see "N groups exist but stayed below K" — that is how reading the portfolio never becomes reading one customer. Consumption considers the customers' goods receipts whose issuer is YOUR tax id.

A platform process computes, every 6 hours, what each customer consented to and publishes it here. The panel never reads the customers' databases directly. "Publication" in the corner shows the last run.

The WhatsApp (30 days) column shows, for each account that lets you see its usage, how many conversations it had, how many the automatic service solved without a person and in how many minutes the customer got the first reply. The table by salesperson adds up each of your salespeople's accounts. You never see the conversations, customers' numbers or who in the store answered — only the account totals, published with the health scale.

Each account invited by the program has "Who pays": the program (default) or the store. An account paid by the program has no billing of its own; the partner gets ONE charge per month with the sum of the plans (Bill this month’s portfolio button — running again in the same month does not charge twice). Switching takes effect next cycle. Stopping payment for an account e-mails the store 30 days ahead: it takes over the plan or the account moves to Free, without losing data.

An invite not accepted for 7 days can go out again with the "Resend invites idle for 7 days" button — the same link is sent, and the next resend only after another 7 days. On each pending invite, "Send via WhatsApp" opens WhatsApp with the message and link ready; you choose the contact. In the bulk invite, the 5th field of the line is the sales rep who serves the account (tax ID; name; e-mail; program code; sales rep); the portfolio gets the sales rep filter and the Sales rep column, so each one looks after their group.

Three models, one per partner. Partner pays per active account: the monthly consolidated charge adds up the plan of active accounts paid by the partner; an account still being onboarded charges no one. Member pays with a discount: each member has their own subscription, with the program discount percentage. Commission to partner: the member pays full price and the partner receives the percentage (with no percentage, the network rate applies, 10%). The panel shows active accounts and who pays what in the month. Only BMCode changes the model.

Grey = the customer does not even share usage. Green, yellow and red only appear for those who chose Usage or above. Ask your representative to explain the benefit: most choose Usage once they understand it is just "I am using it or I stopped".