You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Posting at the right time is one of the most consistent variables affecting organic reach and engagement, yet most social media managers still rely on generic best-practice guides that recommend the same posting windows for every account regardless of their unique audience behaviour. This feature request proposes an AI Optimal Posting Time Engine built natively into TryPost that analyses each connected account's historical performance data, audience activity patterns, and platform-specific signals to automatically recommend and apply the best posting time for every piece of content removing guesswork entirely and replacing it with account-specific intelligence.
Summary
An AI engine that learns from each connected account's historical post performance and audience engagement patterns to generate personalised optimal posting time recommendations per platform, per account, and per content type. When scheduling a post, users can choose to let TryPost automatically assign the best available time slot rather than picking one manually and the engine continuously improves its recommendations as new performance data comes in.
Why This Matters
Generic posting time advice "post on LinkedIn Tuesday at 9am" is based on aggregated industry data that has no relationship to a specific account's actual audience. A SaaS founder's LinkedIn audience behaves completely differently from a fashion brand's Instagram audience. The only way to find the true optimal window for a given account is to analyse that account's own data over time. An AI engine that does this automatically and applies it at the point of scheduling is a compounding advantage the longer a user stays on TryPost, the smarter their scheduling becomes, creating genuine platform lock-in through personalised intelligence that cannot be replicated by switching tools.
Proposed MVP
Analyse each connected account's historical post performance to identify engagement patterns by day, hour, content type, and platform
Display a visual heatmap per account showing high, medium, and low engagement windows across the week
"Best Time" toggle in the composer that automatically assigns the next available optimal time slot when enabled
Separate optimal time recommendations per content format video, carousel, single image, and text-only posts perform differently and are treated distinctly
Audience activity overlay showing when the account's followers are most active on each platform based on available API data
Confidence indicator showing how much historical data the engine has for each account new accounts receive general best-practice defaults that are progressively replaced by account-specific learning
Weekly digest showing which scheduled posts were assigned optimal times and a summary of how posting time has correlated with performance over the preceding period
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Posting at the right time is one of the most consistent variables affecting organic reach and engagement, yet most social media managers still rely on generic best-practice guides that recommend the same posting windows for every account regardless of their unique audience behaviour. This feature request proposes an AI Optimal Posting Time Engine built natively into TryPost that analyses each connected account's historical performance data, audience activity patterns, and platform-specific signals to automatically recommend and apply the best posting time for every piece of content removing guesswork entirely and replacing it with account-specific intelligence.
Summary
An AI engine that learns from each connected account's historical post performance and audience engagement patterns to generate personalised optimal posting time recommendations per platform, per account, and per content type. When scheduling a post, users can choose to let TryPost automatically assign the best available time slot rather than picking one manually and the engine continuously improves its recommendations as new performance data comes in.
Why This Matters
Generic posting time advice "post on LinkedIn Tuesday at 9am" is based on aggregated industry data that has no relationship to a specific account's actual audience. A SaaS founder's LinkedIn audience behaves completely differently from a fashion brand's Instagram audience. The only way to find the true optimal window for a given account is to analyse that account's own data over time. An AI engine that does this automatically and applies it at the point of scheduling is a compounding advantage the longer a user stays on TryPost, the smarter their scheduling becomes, creating genuine platform lock-in through personalised intelligence that cannot be replicated by switching tools.
Proposed MVP
Analyse each connected account's historical post performance to identify engagement patterns by day, hour, content type, and platform
Display a visual heatmap per account showing high, medium, and low engagement windows across the week
"Best Time" toggle in the composer that automatically assigns the next available optimal time slot when enabled
Separate optimal time recommendations per content format video, carousel, single image, and text-only posts perform differently and are treated distinctly
Audience activity overlay showing when the account's followers are most active on each platform based on available API data
Confidence indicator showing how much historical data the engine has for each account new accounts receive general best-practice defaults that are progressively replaced by account-specific learning
Weekly digest showing which scheduled posts were assigned optimal times and a summary of how posting time has correlated with performance over the preceding period
Beta Was this translation helpful? Give feedback.
All reactions