Marketing Hub
Marketing Hub
The home base where FranNet consultants shape their profile, publish, and grow, all in one place.
Sign in to manage your consultant page.
Sign in with GoogleAccess is by invitation, using your @frannet.com Google account. No account? Contact marketing@frannet.com to get set up.
Marketing Hub
Your login works, but it isn’t connected to a FranNet consultant profile yet. Ask your FranNet admin to link your account to your page, then refresh.
Questions buyers are asking Google and AI tools right now. Claim one and write it from your own experience. You can hold 2 ideas at a time, and each claim lasts 21 days.
Loading…
Approved posts only.
No approved posts yet this quarter. Yours could be the first.
Everything you’ve submitted, with its moderation status. You can edit or remove your own.
Loading…
Drafts are sent to FranNet for review before they go live. Nothing publishes automatically. Every published post becomes a new page that can rank in search and feed AI answer engines.
Reviews are moderated before publishing. You must have the client’s permission to share their words. Approved reviews show on your page as proof for the people reading it. (Star ratings in Google search come from your Google Business Profile, so send happy clients to your “Leave a Google review” button too.)
Loading…
Get help using your Marketing Hub. Ask the assistant below, or email the FranNet team directly.
Email support@frannet.comBest practices, approved vendors, and the latest updates from the FranNet marketing team. A reference library to help you get the most out of your page.
Loading…
The latest changes in the Hub, newest first.
When FranNet posts on LinkedIn, share it with your network in a tap. A line in your own words gets it seen by more people.
Loading…
What is booked ahead, in your local time. These are read-only. The team schedules them for you.
Loading…
A minute each. Your notes are what move a meeting from held to counted.
Loading…
These prospects joined. Open each one and say whether they were the right profile.
What you have already told us. Once an outcome is saved, it can't be changed here.
Need to change a past appointment? Email support@frannet.com.
Loading…
Meetings you flagged, or that the FranNet team recorded for you. A flagged meeting does not count toward your package until the FranNet team decides.
Appointments canceled in Calendly. If one actually happened, or the prospect didn't show, tell us here.
Booked-and-showed appointments, delivered to you. You pay once, up front, and only meetings that actually happen count toward your package.
Loading…
Only things waiting on a decision. Empty queues stay out of the way.
Scheduled jobs and reminders the Hub knows about.
Blog articles and client reviews consultants submitted, waiting for review. Approve to publish, or reject to send it back for changes (the consultant is emailed).
Short notes about what is new in the Hub. A published update goes on every consultant’s What’s new page and, if you choose, pops up once for each of them. Drafts are only seen here. No email is sent.
Which design the Hub shows. Every screen, button and rule works the same in both: only the look changes. A change reaches an open Hub the next time it is opened or brought back to the front.
Whether each operational setting is configured, when the daily background job last ran, and the off-site backup, checkable here without opening the Render dashboard. Shows only whether a secret is set, never its value.
Answers come only from what the Hub stores about them, and say so when the Hub does not have it. It cannot change, send or approve anything.
Best-practice articles, approved vendors, and updates. Consultants see published entries only. Entries carry markdown and images; the six-month view and the tips bar are the short version of this deeper guidance.
Every PPA enrollment, newest first. A red marker means a notice failed to send. Use Resend. Check Billed once accounting has handled it (unbilled packages over 48h alert the team and appear in the daily digest). The October offer button appears only on a package the promotion can upgrade; it shows what will change and the exact email before anything happens. Click a row for its submission ID and the rest.
One-time setup: import the historical packages and meetings, compare the Hub's numbers to the tracker, then register the Calendly webhook. Dry run first: it writes nothing. The CSVs stay in memory and are never saved to disk.
Needs CALENDLY_TOKEN set in Render first. Registers one org subscription for invitee.created / invitee.canceled; re-running is safe.
If a commit was wrong, delete exactly its batch. The test package and any live bookings are never touched.
The roster’s Calendly address is an assertion nobody has checked. Bookings attach by an exact match on it, so one wrong character means that consultant’s meetings arrive attached to nobody. Read-only. Nothing here sends an invitation or edits an address.
Press “Check now” to compare against Calendly.
How many more bookings each consultant can still absorb: bookings needed = remaining ÷ conversion rate, minus what is already booked ahead. The rate is derived from live data on a rolling window, never hardcoded. Recomputed on every read. Nothing here is cached, because a meeting’s time passing changes the answer and fires no event.
Every trigger, what it decided, and whether anything was written. In shadow mode nothing is ever written. That is the evidence, not a fault.
No-shows waiting for your decision. Two kinds come here: a no-show marked 14 or more days after the meeting (nothing is recorded until you decide), and a no-show on a meeting that counted as held automatically because nobody marked it within 14 days (it keeps counting until you decide). Approving records the no-show and gives back an appointment. Declining a late no-show records the meeting as held, so it counts toward the package. Any other change comes in by email to support@frannet.com.
Pending disputes first. Click a row to read the reason and the conversation, then approve to remove the appointment from billable, or reject to keep it. Both are logged with your name. The 30 imported disputes appear here to clear.
Every package with the engine's live numbers. Filter by status or consultant, and click a row for the full detail: booked, billable, under review, billed state and submission ID.
Calendly’s four numbers for any range, worked out from the Hub’s records so they can be checked against Calendly Analytics, then what Calendly can’t show: show rate, right profile and disputes. Days and hours are Mountain Time, and each number is compared with the same number of days just before.
Every appointment across the program. Filter by feedback state, consultant, and date. Click a row to see it in full and correct its feedback (attributed to you), the escape hatch for imported-data anomalies.
Every package exactly as the Hub's engine computes it. Green means nothing is internally adrift: every Calendly host maps to a consultant, and every meeting is assigned to a package. It does not mean the Hub agrees with the tracker sheet. That comparison reads the sheet's own Status column and happens only at import time, under PPA go-live → Dry run; to re-check agreement, re-export the CSVs and dry-run again.
The booked-date rule, going forward only. Nothing that exists when it is switched on ever moves: every meeting keeps its package, or no package, and meetings already booked are placed the old way when they happen. A meeting booked after the switch counts toward a package only if it was booked on or after that package's enrollment date, a package never holds more than its size, and a billable meeting with no eligible package that has room is Extra, on FranNet, counted against no package. The check below lists only what applies from now on and changes nothing. Only the button changes anything, after a confirmation.
Each consultant's Calendly seat and pause state. Unmatched Calendly hosts appear at the bottom. Map one to a consultant to assign its meetings.
Three consultants to reach, chosen by what the CRM and the Hub say about them. Reaching someone means a meeting or an email. When all three are logged the week is clear.
Why they are in the outreach ranking, every conversation logged with them, and the form to log the next one.
Whether the promise is being kept: everyone reached inside two quarters. Standing is how the team reads each consultant, counted once per quarter under their most recent read.
Monthly BrandWide files for the Outreach queue. Pick one or more monthly CSVs (brandwide_funnel_YYYY-MM.csv) together with periods.json. Check files first: nothing is written until you press Load and confirm, and Load only works for the exact files that passed the check.
Each set has its own tasks and runs between a start and an end, in the set’s own time zone (New York unless you choose another when you create the set). A task can also open and close on its own times. A set counts points or entries (entries suit a prize drawing), and they count only while it is live; before it starts, consultants see the tasks locked with the start time.
Every completion, newest first. Undo takes the points (or entries) off, and the consultant sees "Removed by the FranNet team" with your reason. Hiding a photo takes it off the shared feed only.
The questions consultants claim and write. Retire an idea to take it out of the bank, or edit its wording. A bank file import adds new ideas and updates the wording of ideas nobody has claimed or written. It never deletes an idea, and never changes one that is claimed or written.
Approved posts per consultant in the quarter, New York time. A post counts once, at its first approval in the Hub, for the person who sent it in. It stops counting if it is deleted, or if an edit is sent back (until an edit is approved). Posts published straight from WordPress do not count. A tie goes to whoever reached that count first.
Every image in a consultant blog post, with where the consultant said it came from. Images from before the source rule are marked Source unknown; nothing about them has been changed.
Every logged action across all consultants, newest first.
Send yourself a sample nudge to check it, see the ledger of what has sent, and dry-run what the next daily run would send right now. Two nudge types: the finish-setup reminder (incomplete pages) and the six-month page review (item 2).