Questions on
your mind.
From deployment and connections to daily work and service scope. Clear answers to your first questions.
Who is Pusula.Social designed for?
Agencies managing social media for several brands. Client workspaces, team permissions, content approvals and reports are brought together around that way of working.
Can we use our own domain?
Yes. The product is deployed separately for each customer. Hosting, the domain, maintenance and backup requirements are agreed during the deployment conversation.
Does every network support every feature?
No. Publishing, analytics, comments and private messages are separate capabilities. The network, account type, connection, permissions and provider plan all affect availability.
Do we need our own API application?
You can use your own API application or a supported managed provider. Some direct connections need only an access key, while others require a domain-specific OAuth application and permission process.
Are social and AI services charged separately?
Additional charges may apply depending on the service and plan. Managed providers, network APIs and AI usage are assessed separately and clarified when discussing deployment.
Does approval immediately publish a post?
No. Review and publishing are separate steps. Timing and target accounts are managed independently; a content change after approval requires another review.
What will we see in a demo?
We explore a workspace, content preparation, review and publishing around your client and team structure. We also clarify the connection requirements of the networks you need.
Does all data stay on our server?
Panel data is stored in your installation. Relevant data is sent to the external services you choose for publishing and AI. A separate installation does not remove those external dependencies.