Re: [bitfolk] How to handle unresponsive customers with issu…

Top Page

Reply to this message
Author: Adam Spiers
Date:  
To: Andy Smith
CC: users
Subject: Re: [bitfolk] How to handle unresponsive customers with issues that cannot be ignored
On Mon, Dec 19, 2016 at 12:55:24PM +0000, Andy Smith wrote:
>Hello,
>
>On Mon, Dec 19, 2016 at 12:49:11PM +0000, Adam Spiers wrote:
>> On 19 December 2016 at 12:45, Andy Smith <andy@???> wrote:
>> > That's obviously not clear enough. How could it be improved?
>>
>> Just ditch the pull-down? It's not as if the add contact page is too
>> long and needs to be kept short.
>
>How would you then pick amongst the four (and soon to be more)
>different things you could add?


Just have all the fields immediately available.

>What about if the initial text was "Select detail to add…" instead of
>it starting off with the suggestion of "Company name…" ? Thus
>inviting you to click.
>
>> There's another problem: there doesn't seem to be any way to add phone
>> numbers to an
>> existing contact, only to a new one. Surely I don't have to delete a
>> contact and re-add it,
>> just to add a phone number?
>
>Underneath the contact is a "change" button. Does that not let you
>add a phone number? It does for me.


Ah, I see that now thanks. But again that's pretty unintuitive to me.
I would expect that button to change the /association/ between a
contact and the alerting role, not to change the contact's details.
And also the most conspicuous place to change the details of the main
contact is in the first section, so it doesn't seem logical that you
can only change certain fields via that section, and not add phone
numbers etc.

It looks like the schema contains tables for the main contact,
secondary contacts, roles, and the role_contact association between
roles and secondary contacts. Is that right? If so I think that's
the source of some of the confusion, because all contacts should be
equal for the most intuitive UI, which would also allow the primary
and secondaries to be interchangeable.

I'd suggest asking a UI/UX designer how to do this better.