# PayWise — TASKS > Living file, merged from meeting notes. Coordenadas scope only. > Last updated: 2026-11-06 · Source meeting: 2026-11-04 · Language: EN (brand TARGET_LANG) > Source meetings: [2026-11-04 — Register button request (Half-Click message)](01_knowledge_base/research-and-notes/meetings/PayWise_Message_2026-11-04_register-button.md) · [2026-06-03 — Monthly higher-ups review](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) ## Active | ID | Task | Owner | Priority | Status | Target date | Origin | |---|---|---|---|---|---|---| | PW-001 | **Recurring monthly PayWise performance report** — one document pulling app install/uninstall (Play Store + App Store), Search Console, social and platform data, refreshed every month. *(long-term / recurring — Agent 10)* | Coordenadas | High | In progress | — | [2026-06-03](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) | | PW-002 | **Build the verified baseline dataset** — export "true values" from Play Store (Android) + App Store + Search Console + social, publish as the source of truth, then layer integrations on top and reconcile them against it. *(long-term / foundational)* | Coordenadas | High | In progress | — | [2026-06-03](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) | | PW-003 | **Lifecycle/engagement emails to the existing base** — bill-payment reminders timed to real bill cycles + how-to guides for users who haven't transacted. *(ongoing program)* | Coordenadas | Medium | Pending | — | [2026-06-03](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) | | PW-004 | **Error follow-up flow** — formally specify the event/data PayWise must expose when a user hits an onboarding/payment error, then set up the customer follow-up email/journey. | Coordenadas | Medium | Pending | — | [2026-06-03](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) | | PW-005 | **TikTok channel** — coordinate creating the account from Trinidad (IP-locked) and, once created, connect it to the platform for posting. *(coordinate side; client creates the account)* | Coordenadas (with Sylvannas) | Medium | Pending | — | [2026-06-03](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) | | PW-006 | *(exploratory)* Analyze social message/interaction volume + categories (complaints, questions, support/API) to inform content priorities. | Coordenadas | Low | Pending | — | [2026-06-03](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) | | PW-009 | **Add a "Register" button to the PayWise website** — button labelled "Register" linking to `https://register.paywise.co`, where visitors submit their documents and PayWise creates the account in the back end. *(new registration path; wording must pass the brand-voice guardrails)* | Coordenadas | Medium | Pending | — | [2026-11-04](01_knowledge_base/research-and-notes/meetings/PayWise_Message_2026-11-04_register-button.md) | ## Blocked | ID | Task | Owner | Blocked by | Origin | |---|---|---|---|---| | PW-007 | Include iOS (App Store) install metrics in the baseline report | Coordenadas | Apple ID / iOS device access from PayWise | [2026-06-03](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) | | PW-008 | Advertise the activation incentive (reward for linking a bank account / completing a first bill payment) | Coordenadas | PayWise must define the reward (PayWise credits, etc.) | [2026-06-03](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) | ## Completed | ID | Task | Owner | Date | Origin | |---|---|---|---|---| | — | — | — | — | — | ## Out of scope (client opportunities / follow-ups) | # | Item | Owner | Note | |---|---|---|---| | 1 | Payment-method selector: dropdown → radio buttons | PayWise (Ian → Nathaniel) | UI change; surfaces wallet/card options | | 2 | Rework the bill-payment flow to cut drop-off | PayWise | product | | 3 | Investigate "Ready to Pay" vs completed bill-payment metric discrepancies | PayWise (Ian/Phill) | data | | 4 | Fix event ingestion into the DB + business/personal double counting | PayWise (Phill, with Elish) | backend | | 5 | Improve the registration flow and reduce post-registration drop-off | PayWise | product | | 6 | Provide last-year new-account creation dates | PayWise (Ian) | data dependency for reporting | | 7 | Provide the user email list (+ business/personal flag, phone) | PayWise (Ian) | Pablo asked for it; needed for WhatsApp/email targeting | | 8 | Provide Apple/iOS App Store access for metrics | PayWise | blocks PW-007 | | 9 | Create the TikTok account from Trinidad (IP geo-locked) | PayWise (Sylvannas) | unblocks PW-005 | | 10 | In-app onboarding / wallet top-up error handling | PayWise | product | ## Change log | Date | Change | Origin | |---|---|---| | 2026-11-06 | Intake of the 2026-11-04 Half-Click message (register.paywise.co): added PW-009 (Register button → `https://register.paywise.co`, active). The document-upload + back-end account creation flow stays a PayWise obligation (related: out-of-scope #5). Saved the raw message + cleaned record under `01_knowledge_base/research-and-notes/meetings/`. No proposals (no new projects/epics/milestones). Uncertainty: message sender inferred from the attachment filename; "the website" assumed to be `paywise.co`. | [2026-11-04](01_knowledge_base/research-and-notes/meetings/PayWise_Message_2026-11-04_register-button.md) | | 2026-09-23 | File created (first TASKS.md for PayWise). Added PW-001…PW-006 (active) and PW-007…PW-008 (blocked); logged 10 client follow-ups. Assessed **not carried** (window passed, superseded by cycles 07_JUL-AUG and 09_SEP): June educational-content schedule and the one-off June bill-payment reminder/engagement push. No tasks marked Done — no completion evidence in the source. | [2026-06-03](01_knowledge_base/research-and-notes/meetings/PayWise_Meeting_2026-06-03_higher-ups-monthly.md) |