Social Office is a set free and open source tools (mainly in spanish) for Social Media Marketing, Digital Marketing, Social Managers, Community Managers, by Javier Cañon
Social CRM has applications in marketing, customer service and sales, including:
- Social Engagement with prospects: SocialCRM tools allow businesses to better engage with their customers by, for example, listening to sentiments about their products and services.
- Social Customer Service: Ownership of social media is shifting away from Marketing and Communication as engagement increasingly relates to inbound customer service-based topics. Rather than social being seen purely as a space for companies to deliver outbound marketing messages, it is the inbound customer queries that allow for meaningful points of engagement and the building of brand advocacy.
- Personalized Marketing Strategy: The ability to create custom content is increasingly dependent on access to reliable, qualitative social user data to facilitate precise audience segmentation. Furthermore, dynamic audience segments, built on both social data and demographic data, allow for more accurate measurement of campaign KPIs.
Traditional customer relationship management focuses on collecting and managing static customer data, such as past purchase information, contact history and customer demographics. This information is often sourced from email and phone interactions, commonly limited to direct interactions between the company and the customer. Social CRM adds a deeper layer of information onto traditional CRM by adding data derived from social networks like Facebook, Twitter, LinkedIn or any other social network where a user publicly shares information. The key benefit of social CRM is the ability for companies to interact with customers in a multichannel retailing environment (commonly referred to as omnichannel) and talk to customers the way they talk to each other. Social CRM enables companies to track a customer's social influence and source data from conversations occurring outside of formal, direct communication. Social CRM also allows companies to keep a full audit history of all customer interactions, regardless of social channel they choose to use, available to all customer care employees.
Metrics for building awareness:
- web traffic
- search volume trends
- volume of followers
- social mentions
Metrics for increasing sales:
- website traffic
- social mentions
- volume of followers
- repeat visits
- social content acceptance rate
Metrics for assessing changes environment in an industry:
- Share of Voice (how much of the overall voice a single brand consumes)
-
KISS by design and programming. An acronym for "keep it simple, stupid" or "keep it stupid simple", is a design principle. The KISS principle states that most systems work best if they are kept simple rather than made complicated; therefore, simplicity should be a key goal in design, and unnecessary complexity should be avoided. Variations on the phrase include: "Keep it simple, silly", "keep it short and simple", "keep it simple and straightforward", "keep it small and simple", or "keep it stupid simple".
-
Select the best tools for the job, use tools that take less time to finish the job.
-
Productivity over complexity and avoid unnecessary complexity for elegant or beauty code.
-
Computers are machines, more powerful every year, give them hard work, concentrate on being productive.
For use only in one computer/machine. Minimum recommended standalone machine configuration:
- Windows 10 64 bit.
- 8 Gigas RAM.
- CPU Intel Core I3 or AMD equivalent.
- 50 Gigas of free space.
- Requires .Net Framework 4.7.2.
- Requires IIS 10 Express 64 bit.
- Requires SQL Server 2017 Express [1].
[1] Limitations : Microsoft SQL Server Express supports 1 physical processor, 1 GB memory, and 10 GB storage.
For multiuser, client/server using LAN network or Internet. Minimum recommended server machine configuration:
- 8 Gigas RAM.
- 4 CPU Cores in virtual servers.
- CPU XEON or Intel Core I7 in dedicated servers.
- 50 Gigas of free space.
Minimum recommended clients machine configuration:
- Windows 10 64 bit.
- 8 Gigas RAM.
- CPU Intel Core I3 or AMD equivalent.
- 50 Gigas of free space.
- Requires .Net Framework 4.7.2.
- Requires IIS 10 enabled in server.
- Requires SQL Server 2017 Web, Standard, Datacenter or Enterprise [1].
[1] Compare SQL Server 2017 Editions.
- No downloads yet.
Things that you need to install the software and how to install them
- Windows 10 64 bits (may works on 7.x and 8.x 64 bits but not tested).
- .Net Framework 4.7.2.
- Sql Server 2017 (any version).
- IIS 10 (Internet Information Server).
A step by step series of examples that tell you how to get a development env running
Say what the step will be
Give the example
And repeat
until finished
End with an example of getting some data out of the system or using it for a little demo
Explain how to run the automated tests for this system
Explain what these tests test and why
Give an example
- MSDN General Naming Conventions
- DoFactory C# Coding Standards and Naming Conventions
- MSDN Naming Guidelines
- MSDN Framework Design Guidelines
First, anything that a user can interact with, or just be shown, is a view. The laws, behavior and characteristics of such a view is described by an interface. That interface can be implemented using a WinForms UI, a console UI, a web UI or even no UI at all (usually when testing a presenter) - the concrete implementation just doesn't matter as long as it obeys the laws of its view interface.
Second, a view is always controlled by a presenter. The laws, behavior and characteristics of such a presenter is also described by an interface. That interface has no interest in the concrete view implementation as long as it obeys the laws of its view interface.
Third, since a presenter controls its view, to minimize dependencies there's really no gain in having the view knowing anything at all about its presenter. There's an agreed contract between the presenter and the view and that's stated by the view interface.
The implications of Third are:
The presenter doesn't have any methods that the view can call, but the view has events that the presenter can subscribe to.
The presenter knows its view. I prefer to accomplish this with constructor injection on the concrete presenter.
The view has no idea what presenter is controlling it; it'll just never be provided any presenter.
Add additional notes about how to deploy this on a live system
Please submit bug reports or feature requests on GitHub.
This project is licensed under the GNU AFFERO GENERAL PUBLIC LICENSE Version 3 - see the LICENSE.md file for details.
Made with ❤️ by Javier Cañon.