On 10 Feb 13:50, Axel Braun wrote: > Hi Ced, > > > Gesendet: Montag, 09. Februar 2015 um 19:37 Uhr > > I wrote a blueprint to manage customer complaint and actions to take. > > http://code.google.com/p/tryton/wiki/CustomerComplaint > > > > The idea is to have a simple but robust basis that allow customization > > especially for actions to take. > > The action processing will be quite similar to the account_payment > > processing. > > Good idea to have CRM functions in Tryton as well.
You can put any acronym you want. > The blueprint is already very technical :-) so what process did you have in > mind? > > How does the registration of the complaint work? You create a record and by you I mean what ever you want. > Out of free space or against e.g. sales, deliveries or purchases? I don't understand the question. But a complaint can be linked to an other record. > Can the clerk check against these elements? Check what? > What are the qualification criteria for a complaint? There is a type. > How should the approval process work? I thought it was obvious with the order of state selection: 'draft' → 'waiting' → 'approved' → 'done' > Actions: > Free of charge delivery It is too late otherwise the customer will not complaint about the charge as it will not yet received it. But you can credit the delivery charge. > Offer bonus payment What is that? > Offer alternative delivery (different product) I don't understand. > Historize: Is this the funcionality that you can see what user did which > activity, when mails were send etc? I don't know. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
