At the moment when you send a campaign mailshot, you can include an 'unsubscribe' page which allows people to unsubscribe from all future mail, or from individual campaigns which they've *already* received email from.

We'd like to extend this so you could include future possible campaign mailshots on the same page, allowing opt-in as well.

eg: You run one general 'Newsletter' mailshot to all customers, but use that page to allow them to opt into more specific campaign newsletters on sub-topics if they wish to.
Or a one-off campaign mailshot after an exhibition to new leads allows people to opt in to your general newsletter campaign.
(Where 'opt in' obviously means they've not received a mail from that campaign before).

We don't want to show all campaigns on the subscribe / unsubscribe page (many are internal only) but a 'Allow mailshot opt in' flag or something along those lines on each campaign might work.

Have you thought of integraHave you thought of integrating with Kashflow? It's a book keeping system that integrates with CRMs and even online payment merchants like paypal etc... They offer a trial period to allow you check them out and are much more user friendly that sage and much mor eaffordable. Key benefits are it helps SME's with VAT returns, Profit & Loss Statements, Invoicing etc... It's near enough an accountant replacement for many services. Saying that, what's great about it is that many accountants work with Kashflow as they too can be granted access on their own interface. That way as a customer you are accessing your records and so are yoru accountants.

- A case is a project linked to a service or item purchased by a customer -- it is linked to an account and require actions to achieve an outcome by a certain deadline. This action may require document sharing, access to knowledge base, communication with team members...

- A campaign is a project linked to a service or item to be purchased by a costumer...

- A service is a project linked to a contract with a customer...

Those are project items that shares common characteristics. They can be segregated under different view or layout but at their core they are identical objects.

It takes time to customise a system with picklist values, custom fields, custom page layouts & default saved user views (last two features are due very soon).

It would be great to have a feature that allows customisation to be exported from one database to another. Maybe there could be a copy customisation from Database A to Database B option. This feature would need to allow you to choose which customisation you need to copy. For example, you may want the picklist values and custom page layouts, but you may not want the saved views. There could even be an export customisation as a file that could be imported and run on another account (not just a from one database to another database within the same account).

I don't think records / object data would need to be exported as this is already exportable via the Export Database feature.

Custom fields already offer the ability to add new fields with the field name you require. However, you can't currently rename standard fields, or include translations to other languages. e.g. Your company may refer to support Cases as Tickets and it would be useful to be able to be able to rename Cases to Tickets.

This will make adoption of Workbooks easier as your users will be familiar with the terms and menu options Start > New > "Ticket" instead of the standard Start > New > Case.

Also, if your company operates in more than one language then you could have the English word for Case, as well as other languages. It would be ideal if Users and System Administrators could define their language in their Preference settings.