Single Source of Truth

\# 360pulse – product specification this document provides a single source of truth for 360pulse it is designed to serve as a reference when creating product specs, ux/ui designs, marketing collateral, technical documentation, and more the goal is to ensure all stakeholders and supporting ais have consistent, accurate information about 360pulse’s current functionality and scope \ \## 1 overview 360pulse is a recurring satisfaction measurement platform, enabling businesses to send short, regular “pulse checks” to their customers (or end users) the key objectives are 1\ gather ongoing feedback (satisfaction over time) 2\ aggregate and present data for easy review and trend analysis 3\ prompt satisfied users to leave testimonials and google reviews \### 1 1 primary use case \ service oriented businesses (e g , msps, agencies, consultants) wanting a quick, repeatable way to measure client satisfaction each month/quarter and track changes over time \### 1 2 product positioning \ not a general purpose survey system \ focused on recurring (scheduled) short surveys, with a strong emphasis on trend analysis and testimonials \ \## 2 key features below is a detailed feature breakdown for the initial product release if a feature is not mentioned, assume it is out of scope at this time \### 2 1 "pulse check" surveys 1\ question format \ each pulse check can have up to 10 questions maximum \ each question can be answered by choosing one of three icons/labels happy , meh , or sad (3 point scale) \ additionally, there is one nps style question at the end (scale 0–10) 2\ scheduling \ pulse checks can be configured to send monthly , quarterly , semi annually , or annually \ an automated process triggers email invitations to contacts at the chosen frequency \ the scheduler supports advanced rules, such as “every x months on \[the nth day / the first monday / the last weekday],” etc \ timezone defaults to the admin’s local browser time and is stored in the database as utc \ one time override the admin can edit the upcoming pulse check date/time without changing the rule \ permanent changes the admin can reopen the scheduler modal and adjust the recurring rule itself 3\ automated reminders \ if a contact does not respond within a configurable number of days, up to two reminder emails can be sent automatically \ goal increase response rates without spamming 4\ multi language support \ each question can have multiple language variants \ the survey detects the browser language and auto selects the corresponding variant if available, else defaults to a fallback language \ a language dropdown on the survey page allows manual switching \ ai powered translations available as an option when editing questions (admin can click a button to get an ai generated translation) \ if a new language is added to a pulse check, the system automatically uses ai to translate existing questions into that language 5\ branding \ the pulse check page (the page the recipient sees) can be styled with the company’s (the 360pulse customer’s) logo , primary color , welcome text , and thank you message \ full white labeling (e g , custom domain, removing 360pulse branding in the footer) is not part of the current feature set 6\ anonymous feedback (optional) \ admins can toggle an option when creating a pulse check to make the responses anonymous \ if enabled, the system does not show the contact or client’s identity in the feedback results, only aggregated metrics \ when viewing a client or contact individually, no data is displayed if the pulse check was anonymous (only aggregated statistics appear ) \ \### 2 2 data entities 1\ client \ represents an organization that the 360pulse customer is surveying (e g , an msp’s client) \ can have tags (like “industry healthcare,” “account manager bob”) \ also holds an industry value used for future benchmarking (though no industry benchmarking is delivered at this stage) 2\ contact \ individuals within a client \ fields name, email, optional tags, optional metadata (like job title) \ typically each contact belongs to a single client 3\ survey configuration (pulse check) \ a definition of the recurring schedule (frequency), the question set (1–10 questions + 1 nps question), branding info, language variants, and anonymous on/off 4\ survey instance \ each email invitation to a specific contact at a specific time is an instance \ tracks whether the contact responded, the date/time, and the answers \ \### 2 3 testimonials & google review requests 1\ trigger \ if the final nps score is ≥ 7 , the survey completion page displays options \ leave a testimonial (text area, checkbox to agree to terms) \ create a google review (with a link to the business’s review page) 2\ collection & logging \ if the respondent submits a testimonial, it is stored in the system’s database alongside their name and date (even if anonymous mode is on) \ after a testimonial is collected, do not repeatedly prompt the same user for another testimonial in subsequent surveys \ the system records whether the user clicked the google review link 3\ google review tracking \ the system captures the total number of google reviews and the overall google rating daily \ maintains a historical record of how many reviews exist and the average rating this data can be displayed as a chart to show growth/improvement over time \ \### 2 4 reporting & analytics 1\ admin dashboard \ client list view rows of clients with columns showing \ overall sentiment (color coded or icon coded) for the current period \ up/down arrow indicating if the sentiment is trending compared to the previous period \ subcategory columns (each question category) with a summary icon (happy/meh/sad) \ a final column indicating if any comments or testimonials were submitted \ a button or link to view details for that client 2\ client details view \ shows a timeline (month by month or period by period) of aggregated results \ displays \ average 3 point scale responses \ nps rating each time \ open text comments (if any) \ ability to filter by tags (e g , “account manager bob,” “location us,” etc ) \ exports to csv for that client’s data (only available to admins) 3\ tag based filtering \ admin can apply multiple tags to clients and/or contacts (e g , “tier 1,” “manager alice”) \ filter the entire dashboard to show only results for certain tags, aiding segmentation 4\ no leaderboards / gamification \ no leaderboard or gamified reporting features are included at this time \ \### 2 5 roles & permissions 1\ admin \ full system privileges create/edit/delete pulse checks, clients, contacts, questions, etc \ access to all reporting data across all clients \ can export data to csv \ assign tags, set schedules, manage user roles 2\ user \ can view results for assigned clients/contacts only \ cannot export any data \ cannot modify system settings, schedules, or questions \ \### 2 6 additional details 1\ no complex follow ups \ other than basic reminders, no advanced sequences or multi step follow ups (e g , if negative feedback → auto schedule a call) 2\ no integrations \ this release does not integrate with crms, ticketing systems, or zapier all data entry (clients, contacts) is manual or via csv import 3\ no client/end user portals \ clients being surveyed do not get a login to view or manage their own feedback data only internal 360pulse users (admins, users) can see results 4\ avatar retrieval \ the system attempts to fetch a gravatar or public linkedin avatar by email if not found, it uses a generic placeholder 5\ mobile optimized surveys \ surveys are responsive and easy to fill on mobile devices 6\ guided setup wizard \ for new 360pulse customers \ basic company info (name, logo, industry) \ setup wizard flow 1\ create first pulse check \ add up to 10 questions, define branding (logo, primary color) \ indicate frequency (monthly, quarterly, etc ) \ specify if anonymous \ optionally add language variants; ai auto translates existing questions for the new language 2\ add clients/contacts \ prompt to upload csv or manually add 3\ schedule \ choose “every x months” or “every x quarter(s)/year(s)” with the day of month rules (e g , “1st monday,” “last weekday”) \ defaults to admin’s local timezone, stored in utc 7\ survey preview \ admin can preview how the pulse check looks before sending out 8\ accessibility \ basic accessibility considerations in forms and color contrast \ no formal advanced compliance claims at this time 9\ exports & data ownership \ data belongs to the 360pulse customer \ csv exports are available at the admin level only \ \## 3 system architecture & data model (high level) \| entity | key fields | relationships | \| | | | \| customer (your paying subscriber) | name, industry, user roles\<br> subscription data | n/a | \| client | name\<br> tags\<br> industry (for future benchmarks) | multiple contacts belong to one client | \| contact | name, email, avatar url\<br> tags (optional) | belongs to one client | \| pulse check (survey config) | title\<br> frequency (monthly, etc )\<br> start date\<br> questions & question structure\<br> branding (logo, color)\<br> multi language variants\<br> anonymous flag | each pulse check spawns multiple survey instances | \| survey instance | tied to a pulse check\<br> tied to a specific contact\<br> send date (utc)\<br> completion date\<br> answers (3 point scale, nps, comments)\<br> testimonial, if given | many per pulse check (one per contact, each interval) | \ \## 4 pricing model 1\ contact based \ plans scale based on how many total contacts are active in the system \ example tiers \ free up to 50 contacts, 1 active pulse check \ paid tier 1 up to 500 contacts \ paid tier 2 up to 2,000 contacts \ pricing details tbd 2\ features \ all core features are included in all paid tiers \ free tier has a limited contact count potential limitations could apply to ai rewording or multi language support, but final restrictions are tbd \ \## 5 survey flow 1\ scheduling \ admin configures a pulse check with the desired start date and frequency (monthly, quarterly, etc ) \ selects specific rules, e g , “every 2 months on the fourth saturday at 9 00 am ” \ a background service checks which surveys need to be sent on each applicable day \ one time override admin can change just the upcoming pulse check date/time \ changing the schedule admin can edit the rules at any time, which updates future occurrences 2\ invitation email \ each contact receives a unique link to complete the pulse check online \ the link includes an identifier to track responses 3\ survey page \ displays the brand’s logo/colors (from the pulse check config) \ shows each question (3 point scale) plus an optional comment box \ ends with an nps question (0–10 scale) 4\ testimonial/review prompt \ if the user’s nps ≥ 7 (or if they selected primarily “happy”), the next screen asks \ “would you like to leave us a testimonial?” \ “click here to leave a google review ” \ if the user is below that threshold, the system thanks them for their feedback and does not show review prompts 5\ reminders \ if no response within the configured reminder interval (e g , 3 days), a reminder email is sent \ up to 2 reminders total 6\ result capture \ the system stores the responses \ if a testimonial is given, it is logged in the database with a timestamp and contact name (unless anonymous) 7\ reporting \ admins can view aggregated stats on the 360pulse dashboard or drill down at the client level \ users can only view clients/contacts to which they are assigned (no exports) 8\ google reviews tracking \ the system retrieves the total number of reviews and the overall rating from google daily, storing it for trend charts \ \## 6 currently out of scope to clarify, the current release does not include 1\ multiple survey types (only one short “pulse check” type) 2\ deep/extended surveys 3\ 360 feedback (multi rater feedback loops) 4\ advanced integrations (crm, ticketing, zapier) 5\ ai sentiment analysis (for open text comments) 6\ client/end user portals 7\ leaderboards or gamification 8\ churn prediction 9\ advanced accessibility compliance claims 10\ follow up sequences beyond basic reminders (no advanced triggers for negative feedback) \ \## 7 future roadmap 1\ longer or more detailed surveys \ potential “deep pulse” surveys with more question types, scheduled less frequently 2\ ai sentiment analysis \ automatic detection of positive/negative themes in open text feedback 3\ alerts/notifications \ slack, teams, or email alerts triggered by negative feedback or sudden drops in satisfaction 4\ industry benchmarks \ compare a user’s nps or satisfaction against industry averages once enough anonymized data is gathered 5\ testimonial widgets \ embeddable code snippet to display curated testimonials on the business’s own website 6\ integrations \ crm, ticketing, zapier for automating data flows in/out of 360pulse 7\ lifecycle surveys \ triggered automatically at specific points in the customer journey 8\ white labeling \ removing 360pulse branding entirely for agencies that want a private labeled version 9\ churn prediction \ ai driven correlation of repeated negative scores, inactivity, etc \ \## 8 implementation & next steps 1\ design & branding \ finalize the 360pulse brand identity, color palette, and ui components 2\ database & architecture \ define the schema for clients, contacts, surveys, responses \ implement scheduling logic with monthly/quarterly/etc rules, stored in utc 3\ survey builder \ allow admins to create up to 10 questions \ provide a “start from template” or “start from scratch” workflow \ optional ai rewrite button for question rewording \ optional ai language translation for additional languages 4\ email & reminder system \ integrate with an email service provider (e g , sendgrid, postmark) \ build logic for automated reminders 5\ frontend \ responsive, mobile optimized survey pages with multi language support \ admin dashboard with user role logic 6\ testimonials & google review flow \ admin sets a google review link \ survey completion page prompts users with high scores to submit a testimonial or visit google review link \ automated daily retrieval of google review counts/ratings to show growth over time 7\ reporting \ aggregate reporting (dashboard) with trending over time and filtering by tags \ csv export (admin only) 8\ pricing & payment gateway \ integrate a subscription management system (e g , stripe) \ enforce contact limits per plan 9\ beta testing & feedback \ pilot with a small group to ensure reliability and gather initial user feedback \ \## 9 conclusion this 360pulse product specification defines what the initial version does, how it works, and what is currently out of scope it’s designed to ensure alignment across design, development, marketing, and support future enhancements can be added once the core platform is live and validated, building a complete ecosystem for ongoing, automated satisfaction measurement and testimonial collection end of document